diff --git a/.github/workflows/check-broken-links-github-github.yml b/.github/workflows/check-broken-links-github-github.yml index a0561737f7..d7273d7b20 100644 --- a/.github/workflows/check-broken-links-github-github.yml +++ b/.github/workflows/check-broken-links-github-github.yml @@ -57,8 +57,11 @@ jobs: env: NODE_ENV: production PORT: 4000 + # Overload protection is on by default (when NODE_ENV==production) + # but it would help in this context. DISABLE_OVERLOAD_PROTECTION: true - DISABLE_RENDER_CACHING: true + # Render caching won't help when we visit every page exactly once. + DISABLE_RENDERING_CACHE: true run: | node server.mjs & diff --git a/.github/workflows/sync-search-indices.yml b/.github/workflows/sync-search-indices.yml index d2f3237335..51e0975f74 100644 --- a/.github/workflows/sync-search-indices.yml +++ b/.github/workflows/sync-search-indices.yml @@ -92,6 +92,8 @@ jobs: # Because the overload protection runs in NODE_ENV==production # and it can break the sync-search. DISABLE_OVERLOAD_PROTECTION: true + # Render caching won't help when we visit every page exactly once. + DISABLE_RENDERING_CACHE: true run: npm run sync-search diff --git a/components/DefaultLayout.tsx b/components/DefaultLayout.tsx index 5b89132791..3115036176 100644 --- a/components/DefaultLayout.tsx +++ b/components/DefaultLayout.tsx @@ -27,6 +27,7 @@ export const DefaultLayout = (props: Props) => { const { t } = useTranslation(['errors', 'meta', 'scroll_button']) const router = useRouter() const metaDescription = page.introPlainText ? page.introPlainText : t('default_description') + return (
diff --git a/components/context/DotComAuthenticatedContext.tsx b/components/context/DotComAuthenticatedContext.tsx new file mode 100644 index 0000000000..fcdf071355 --- /dev/null +++ b/components/context/DotComAuthenticatedContext.tsx @@ -0,0 +1,19 @@ +import { createContext, useContext } from 'react' + +export type DotComAuthenticatedContextT = { + isDotComAuthenticated: boolean +} + +export const DotComAuthenticatedContext = createContext(null) + +export const useAuth = (): DotComAuthenticatedContextT => { + const context = useContext(DotComAuthenticatedContext) + + if (!context) { + throw new Error( + '"useAuthContext" may only be used inside "DotComAuthenticatedContext.Provider"' + ) + } + + return context +} diff --git a/components/context/LanguagesContext.tsx b/components/context/LanguagesContext.tsx index 748b59031a..03f2abf18a 100644 --- a/components/context/LanguagesContext.tsx +++ b/components/context/LanguagesContext.tsx @@ -10,6 +10,7 @@ type LanguageItem = { export type LanguagesContextT = { languages: Record + userLanguage: string } export const LanguagesContext = createContext(null) diff --git a/components/context/MainContext.tsx b/components/context/MainContext.tsx index 59755e4797..cb10230c1c 100644 --- a/components/context/MainContext.tsx +++ b/components/context/MainContext.tsx @@ -93,7 +93,6 @@ export type MainContextT = { relativePath?: string enterpriseServerReleases: EnterpriseServerReleases currentPathWithoutLanguage: string - userLanguage: string allVersions: Record currentVersion?: string currentProductTree?: ProductTreeNode | null @@ -125,7 +124,6 @@ export type MainContextT = { status: number fullUrl: string - isDotComAuthenticated: boolean } export const getMainContext = (req: any, res: any): MainContextT => { @@ -181,7 +179,6 @@ export const getMainContext = (req: any, res: any): MainContextT => { 'supported', ]), enterpriseServerVersions: req.context.enterpriseServerVersions, - userLanguage: req.context.userLanguage || '', allVersions: req.context.allVersions, currentVersion: req.context.currentVersion, currentProductTree: req.context.currentProductTree @@ -192,7 +189,6 @@ export const getMainContext = (req: any, res: any): MainContextT => { nonEnterpriseDefaultVersion: req.context.nonEnterpriseDefaultVersion, status: res.statusCode, fullUrl: req.protocol + '://' + req.get('host') + req.originalUrl, - isDotComAuthenticated: Boolean(req.cookies.dotcom_user), } } diff --git a/components/page-header/Header.tsx b/components/page-header/Header.tsx index ddbdc2ede7..b0ca9a6bab 100644 --- a/components/page-header/Header.tsx +++ b/components/page-header/Header.tsx @@ -6,6 +6,7 @@ import { useVersion } from 'components/hooks/useVersion' import { Link } from 'components/Link' import { useMainContext } from 'components/context/MainContext' +import { useAuth } from 'components/context/DotComAuthenticatedContext' import { LanguagePicker } from './LanguagePicker' import { HeaderNotifications } from 'components/page-header/HeaderNotifications' import { ProductPicker } from 'components/page-header/ProductPicker' @@ -17,7 +18,7 @@ import styles from './Header.module.scss' export const Header = () => { const router = useRouter() - const { isDotComAuthenticated, error } = useMainContext() + const { error } = useMainContext() const { currentVersion } = useVersion() const { t } = useTranslation(['header', 'homepage']) const [isMenuOpen, setIsMenuOpen] = useState( @@ -25,6 +26,8 @@ export const Header = () => { ) const [scroll, setScroll] = useState(false) + const { isDotComAuthenticated } = useAuth() + const signupCTAVisible = !isDotComAuthenticated && (currentVersion === 'free-pro-team@latest' || currentVersion === 'enterprise-cloud@latest') diff --git a/components/page-header/HeaderNotifications.tsx b/components/page-header/HeaderNotifications.tsx index 4b696bc5f6..0c5dd4d5f0 100644 --- a/components/page-header/HeaderNotifications.tsx +++ b/components/page-header/HeaderNotifications.tsx @@ -21,9 +21,9 @@ type Notif = { export const HeaderNotifications = () => { const router = useRouter() const { currentVersion } = useVersion() - const { relativePath, allVersions, data, userLanguage, currentPathWithoutLanguage, page } = - useMainContext() - const { languages } = useLanguages() + const { relativePath, allVersions, data, currentPathWithoutLanguage, page } = useMainContext() + const { languages, userLanguage } = useLanguages() + const { t } = useTranslation('header') const translationNotices: Array = [] diff --git a/components/page-header/RestBanner.tsx b/components/page-header/RestBanner.tsx index cc2ea6be56..0a740ed804 100644 --- a/components/page-header/RestBanner.tsx +++ b/components/page-header/RestBanner.tsx @@ -20,7 +20,7 @@ const restRepoCategoryExceptionsTitles = { branches: 'Branches', collaborators: 'Collaborators', commits: 'Commits', - deploy_keys: 'Deploy Keys', + 'deploy-keys': 'Deploy Keys', deployments: 'Deployments', pages: 'GitHub Pages', releases: 'Releases', diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md index 30a3d24ddb..ac1511cb43 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories shortTitle: Manage default branch name --- ## About management of the default branch name diff --git a/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 00b85ef504..2309ae9587 100644 --- a/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -369,6 +369,10 @@ runs: ``` {% endif %} +#### `runs.steps[*].continue-on-error` + +**Optional** Prevents the action from failing when a step fails. Set to `true` to allow the action to pass when this step fails. + ## `runs` for Docker container actions **Required** Configures the image used for the Docker container action. diff --git a/content/actions/security-guides/encrypted-secrets.md b/content/actions/security-guides/encrypted-secrets.md index 1dee8084fb..f94e6f4358 100644 --- a/content/actions/security-guides/encrypted-secrets.md +++ b/content/actions/security-guides/encrypted-secrets.md @@ -342,7 +342,7 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB, - name: Decrypt large secret run: ./.github/scripts/decrypt_secret.sh env: - LARGE_SECRET_PASSPHRASE: {% raw %}${{ secrets. LARGE_SECRET_PASSPHRASE }}{% endraw %} + LARGE_SECRET_PASSPHRASE: {% raw %}${{ secrets.LARGE_SECRET_PASSPHRASE }}{% endraw %} # This command is just an example to show your secret being printed # Ensure you remove any print statements of your secrets. GitHub does # not hide secrets that use this workaround. diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index fad6066c82..1b0bceef68 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -198,6 +198,7 @@ When you call a reusable workflow, you can only use the following keywords in th * [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) * [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) * [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) +* [`jobs..concurrency`](/actions/reference/workflow-syntax-for-github-actions#concurrency) {% note %} diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index f4eca2bb3b..e51012e9cc 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -271,6 +271,15 @@ If the {% data variables.product.prodname_codeql_workflow %} still fails on a co This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)." {% endif %} +## Error: "is not a .ql file, .qls file, a directory, or a query pack specification" + +You will see this error if CodeQL is unable to find the named query, query suite, or query pack at the location requested in the workflow. There are two common reasons for this error. + +- There is a typo in the workflow. +- A resource the workflow refers to by path was renamed, deleted, or moved to a new location. + +After verifying the location of the resource, you can update the workflow to specify the correct location. If you run additional queries in Go analysis, you may have been affected by the relocation of the source files. For more information, see [Relocation announcement: `github/codeql-go` moving into `github/codeql`](https://github.com/github/codeql-go/issues/741) in the github/codeql-go repository. + ## Warning: "git checkout HEAD^2 is no longer necessary" If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: diff --git a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 751f502bac..f503abb34f 100644 --- a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -15,7 +15,7 @@ topics: - Secret scanning --- -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change. @@ -33,7 +33,7 @@ You can define custom patterns for your enterprise, organization, or repository. {%- else %} 20 custom patterns for each organization or enterprise account, and per repository. {%- endif %} -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}: diff --git a/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 7e14e81eae..609fce18c6 100644 --- a/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -38,7 +38,7 @@ To get the most out of your trial, follow these steps: 1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations). 2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see: - - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast + - [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)" diff --git a/content/graphql/guides/forming-calls-with-graphql.md b/content/graphql/guides/forming-calls-with-graphql.md index c23a7d792f..af772ceef7 100644 --- a/content/graphql/guides/forming-calls-with-graphql.md +++ b/content/graphql/guides/forming-calls-with-graphql.md @@ -32,14 +32,14 @@ The following scopes are recommended: ``` -user{% ifversion not ghae %} -public_repo{% endif %} repo -repo_deployment repo:status -read:repo_hook +repo_deployment{% ifversion not ghae %} +public_repo{% endif %} read:org read:public_key +read:repo_hook +user read:gpg_key ``` diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 461bb3da0c..7da1e0c05f 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.3' - ghae: issue-4651 + ghae: '*' ghec: '*' topics: - Repositories diff --git a/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md b/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md index 6ac13a1f41..c2f4e1150c 100644 --- a/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md +++ b/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md @@ -32,4 +32,5 @@ Query parameter | Example ## Further reading -- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating an issue from a URL query](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-url-query)" +- "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request/)" diff --git a/data/release-notes/enterprise-server/3-5/0-rc1.yml b/data/release-notes/enterprise-server/3-5/0-rc1.yml index ddebbe7a5d..31567083ba 100644 --- a/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -141,7 +141,7 @@ sections: notes: # https://github.com/github/releases/issues/1503 - | - You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/managing-workflow-runs/re-running-workflows-and-jobs)." + You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - heading: Dependency graph supports GitHub Actions notes: @@ -373,7 +373,7 @@ sections: # https://github.com/github/releases/issues/2054 - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories)." + New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." # https://github.com/github/releases/issues/2028 - | diff --git a/data/release-notes/github-ae/2022-05/2022-05-17.yml b/data/release-notes/github-ae/2022-05/2022-05-17.yml index b8da1e31db..35509a16db 100644 --- a/data/release-notes/github-ae/2022-05/2022-05-17.yml +++ b/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -21,14 +21,14 @@ sections: - | GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - heading: 'Dependency graph' notes: - | - Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." - heading: 'Dependabot alerts' notes: @@ -74,7 +74,7 @@ sections: - heading: 'Audit log accessible via REST API' notes: - | - You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." - heading: 'Expiration dates for personal access tokens' notes: @@ -135,7 +135,7 @@ sections: - heading: 'GitHub Actions' notes: - | - To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." - | The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. @@ -183,7 +183,7 @@ sections: - heading: 'Repositories' notes: - | - GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - | You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. diff --git a/data/reusables/code-scanning/run-additional-queries.md b/data/reusables/code-scanning/run-additional-queries.md index e74bb3a820..483ad322b5 100644 --- a/data/reusables/code-scanning/run-additional-queries.md +++ b/data/reusables/code-scanning/run-additional-queries.md @@ -15,4 +15,4 @@ Any additional queries you want to run must belong to a {% data variables.produc You can specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)." {% endif %} -{% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, like `github/codeql/cpp/ql/src@main`. Such queries may not be compiled with the same version of {% data variables.product.prodname_codeql %} as used for your other queries, which could lead to errors during analysis.{% endif %} +{% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, for example, `github/codeql/cpp/ql/src@main`. Such queries would have to be recompiled, and may not be compatible with the version of {% data variables.product.prodname_codeql %} currently active on {% data variables.product.prodname_actions %}, which could lead to errors during analysis.{% endif %} diff --git a/data/reusables/enterprise_enterprise_support/support-holiday-availability.md b/data/reusables/enterprise_enterprise_support/support-holiday-availability.md index 32c4107a55..e6221f8f3c 100644 --- a/data/reusables/enterprise_enterprise_support/support-holiday-availability.md +++ b/data/reusables/enterprise_enterprise_support/support-holiday-availability.md @@ -4,7 +4,7 @@ | Martin Luther King, Jr. Day | Third Monday in January | | Presidents' Day | Third Monday in February | | Memorial Day | Last Monday in May | -| Independence Day | July 5 | +| Independence Day | July 4 | | Labor Day | First Monday in September | | Veterans Day | November 11 | | Thanksgiving Day | Fourth Thursday in November | diff --git a/lib/failbot.js b/lib/failbot.js index e63d344f69..10014252e6 100644 --- a/lib/failbot.js +++ b/lib/failbot.js @@ -43,7 +43,7 @@ export async function report(error, metadata) { ] const failbot = new Failbot({ app: HAYSTACK_APP, - backends: backends, + backends, }) return failbot.report(error, metadata) } diff --git a/lib/get-theme.js b/lib/get-theme.js index 50a6e0d181..a4b9b964dc 100644 --- a/lib/get-theme.js +++ b/lib/get-theme.js @@ -1,11 +1,9 @@ -// export const defaultCSSThemeProps = { export const defaultCSSTheme = { colorMode: 'auto', // light, dark, auto nightTheme: 'dark', dayTheme: 'light', } -// export const defaultComponentThemeProps = { export const defaultComponentTheme = { colorMode: 'auto', // day, night, auto nightTheme: 'dark', diff --git a/lib/page-data.js b/lib/page-data.js index 6b471df1a9..4e228b7894 100644 --- a/lib/page-data.js +++ b/lib/page-data.js @@ -263,8 +263,8 @@ export async function correctTranslationOrphans(pageList, basePath = null) { pageLoadPromises.push( Page.init({ basePath: englishBasePath, - relativePath: relativePath, - languageCode: languageCode, + relativePath, + languageCode, }) ) } diff --git a/lib/page.js b/lib/page.js index eacb1ae968..1bc8f7b950 100644 --- a/lib/page.js +++ b/lib/page.js @@ -24,22 +24,6 @@ import { union } from 'lodash-es' // every single time, we turn it into a Set once. const productMapKeysAsSet = new Set(Object.keys(productMap)) -// Wrapper on renderContent() that caches the output depending on the -// `context` by extracting information about the page's current permalink -const _renderContentCache = new Map() - -function renderContentCacheByContext(prefix) { - return async function (template = '', context = {}, options = {}) { - const { currentPath } = context - const cacheKey = prefix + currentPath - - if (!_renderContentCache.has(cacheKey)) { - _renderContentCache.set(cacheKey, await renderContent(template, context, options)) - } - return _renderContentCache.get(cacheKey) - } -} - class Page { static async init(opts) { opts = await Page.read(opts) @@ -186,18 +170,18 @@ class Page { context.englishHeadings = englishHeadings } - this.intro = await renderContentCacheByContext('intro')(this.rawIntro, context) - this.introPlainText = await renderContentCacheByContext('rawIntro')(this.rawIntro, context, { + this.intro = await renderContent(this.rawIntro, context) + this.introPlainText = await renderContent(this.rawIntro, context, { textOnly: true, }) - this.title = await renderContentCacheByContext('rawTitle')(this.rawTitle, context, { + this.title = await renderContent(this.rawTitle, context, { textOnly: true, encodeEntities: true, }) - this.titlePlainText = await renderContentCacheByContext('titleText')(this.rawTitle, context, { + this.titlePlainText = await renderContent(this.rawTitle, context, { textOnly: true, }) - this.shortTitle = await renderContentCacheByContext('shortTitle')(this.shortTitle, context, { + this.shortTitle = await renderContent(this.shortTitle, context, { textOnly: true, encodeEntities: true, }) @@ -205,7 +189,7 @@ class Page { this.product_video = await renderContent(this.raw_product_video, context, { textOnly: true }) context.relativePath = this.relativePath - const html = await renderContentCacheByContext('markdown')(this.markdown, context) + const html = await renderContent(this.markdown, context) // Adding communityRedirect for Discussions, Sponsors, and Codespaces - request from Product if ( @@ -222,15 +206,12 @@ class Page { // product frontmatter may contain liquid if (this.rawProduct) { - this.product = await renderContentCacheByContext('product')(this.rawProduct, context) + this.product = await renderContent(this.rawProduct, context) } // permissions frontmatter may contain liquid if (this.rawPermissions) { - this.permissions = await renderContentCacheByContext('permissions')( - this.rawPermissions, - context - ) + this.permissions = await renderContent(this.rawPermissions, context) } // Learning tracks may contain Liquid and need to have versioning processed. diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index 30497b65d8..d25d630a08 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:45eec45e549fa04df760c2d133744cb6696f0733e6feeb8b2faa6e1cc3fbd0a1 -size 686308 +oid sha256:7a107e0e65d9055f6f2b9e54c22c7a360c480123832ef915738cc38258284724 +size 680760 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index 0653416271..232cb699fc 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0febe199e3ce31c19fc3da32c435a4c788fbca65c2b9b8fad54bdf1320c938ea -size 1336302 +oid sha256:9f7355968bfa6a64f13c7eb1f0cc5c17a8e7da1f101e61e7abaab01b4c80753a +size 1329872 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index d56b931185..9ea8f26876 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:afed828ae58e9fa821eb868144b460830deab7461ccd008081fe4b939b24c2b4 -size 917755 +oid sha256:36f81a82620c46cdde46438bca1db1ad48d29091862cbb2792ab75eb2d56004c +size 909627 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index e3a10131ae..93734ddb4e 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9a733fbc3443c6e1825306dfebfefdbdf6e6c63d7296afc3d481b07589020de6 -size 3537523 +oid sha256:8adc7917c3d2d7d69088934bce3d7f6ec139c4fd6cf119ce1532248a8e6c1eac +size 3527038 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index bd28f1cc30..ac210eafa6 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4ddeef7faeac9aab5e0a06a52f7273ccc5abc28e22f3e8bdde7c19c029f063f1 -size 631967 +oid sha256:5a87568e4289843a381a9e8a8d632a25ac30b5e1bec922c870b7214bd7e5cf4c +size 626755 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index d818638d93..fd0f66c694 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5dcdc5a61778a3c667a3d24da93e1302ba47cae67f1e581341cd0012ce32c1af -size 2663740 +oid sha256:3685c626ed482e1ecd2bcd6a67bc2b6b775faca671d6543fb0c1f1de3641bc4f +size 2646062 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index e807c83f56..3b6ec74739 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:25bb27455088ed2c9597dcd533e3a0fb1b803cfcf8eaeb90ea6853be9dea363e -size 696416 +oid sha256:7fe8e4e4353e253211fb06f76f7e53557dcebb8f3c523d84b9d3a09d107f134f +size 689784 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index 847d87d5f7..7dfc7dbfb2 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:103d6d7ffc934d6bcb6bf990b478bbc8473c2f98ba0ab12fa6cef01c537a83d0 -size 3718970 +oid sha256:2b8b2f0d6d8fe6bc0521ce45fe810bdea526c44a7fc037b3082f2b5b446cc74c +size 3702490 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index cf23eaac72..f2606341f3 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e546eae9071262337a4c3f09ede6af8956038913a9899235ed89ce09f623171a -size 623526 +oid sha256:54d5898d2ff6647f37d86dd338d53ab42325969848b2941f83d46f6c61b64394 +size 616973 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 81deea92d9..70879f7032 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b8d350e16212f96742a75a84ca5671c50da8067c564206663a72c69f18dd4921 -size 2569190 +oid sha256:472672d62d5785aacf297b7f5722733da97ac50f7089176189a8f6162be88cc6 +size 2546010 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index e19a963f37..20df004217 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:aca2ac22c3e40cfd608e1c0bc9505431146e0e37323bd0db902d5a2ff67eab55 -size 704715 +oid sha256:eef3a5142d3377125a29b33d5dc85ec78ed476289e27ba6b5bf04db3f77e8c6a +size 698319 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 584b3d37c8..f67488b646 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d133ff96847920746364eb76d94f5a15cea284d358cd0874620dec1c57bd3af5 -size 1363408 +oid sha256:9a8bd35c2dcb2f2c5d5ac5fd942dbc4b26bf40f97fd4b81348577097bb4ac2c3 +size 1356468 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 7a4a90626f..0be96613d0 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e526f098b0c267d8c757131b14ba32252ac0875729fa578e00d2b27905a364eb -size 948049 +oid sha256:d949b4c26263591daf64d2dfb2c1ca12eb17188a5b9c77e589ee5b846e951448 +size 939384 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index a6d863a166..c38e7d65ca 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1ef62c12f1233390dfe303d670ad2cbd2d83d88c0a73c513faaa512c52e7ac84 -size 3659914 +oid sha256:6bedc1be5b04f2e979b9575e62731fa73e68b695f583cfb918fc7a31f8a7761c +size 3646845 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 4380f67f80..4fcdf449ab 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0938e8d2846ea3b30abf7e70f50bba76dc9d5b263adb2b1e2eab606ab21d05bf -size 649472 +oid sha256:d31b923df1aab7e6f44f5a1e2d7e1aab9e640cc72100a1d1f4cad5718de94faf +size 643281 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index 5e1f897656..1f7d6ca777 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:42ac2ae786f2209445354f579076b95b1b348b5f929f958f1943ff00d7e2c02f -size 2734937 +oid sha256:bf33abe48954e67362f4d0c7516fdab067306e0ed627c71c7ff9cdec6384166e +size 2716898 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index 87f496fdaa..e24063fbb2 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1b403e60ddb4fcfee68b88d593d1579fb44749536a66c110dafd9b11ddc33f6c -size 714194 +oid sha256:9624aae47ad150f40b37bcf4c3193b4e84021b099b8d88de73db612d316647c5 +size 707494 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 4f07f76bf9..769a7feefc 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1c3b5d8c996d10a92a07badbd3af2ac6fbd8330480f3a768e89633bb4f4f5c03 -size 3816188 +oid sha256:10879aea569685065a3843735f5fd0bd476559a3fcbb31c1b386e0e54254b339 +size 3798666 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index e94f500474..464fd0ac29 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4de3bdc9568cbdd01a03850bae30e04ec53faf87b6ae3a51029e668a2d96053a -size 640559 +oid sha256:2569c79ee2766ccd39f50a05ca3101d097b6314640a385e0d77d547cba47c6bd +size 633332 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index 207ac860e0..3c298912c4 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4f8c1b147406b4912f029d507799f5d646b8de061f75d34fb2f17cbe9c373a02 -size 2633542 +oid sha256:35cc96348710bc1c43a235003a180a9aa17c5e98fdff3bda5b107914315342ac +size 2609625 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 52a82106e2..29f3596630 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:29a1ff64014552565706b09f5bf66503bd79bbb5cd7ad010056d5b8ad9c5d9cb -size 728034 +oid sha256:36fdd2ed46ba45b728e5ddb63e1ca1dadcf2d1615b52e2d6b74d078002d243cd +size 721538 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 8adbdde5ac..1188993f77 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:69d4fd297beee66e3c0d4e8ab1f0f839a120ba968da3874c9b52aa1174dbce1b -size 1406961 +oid sha256:db913f55ebddee8261f4b5d725a15f1c75b84d183cc6f825cb8987e2061209ba +size 1399724 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 9d67ae15ed..b109dceae6 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4863bc45cae5ad5bf59993f2ca447860214e67f12c027489192402482c6d5022 -size 982704 +oid sha256:e59fcaa70e7494bd555d2874464650c49a10bebccff631092c8a045df1d69462 +size 974294 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 00a90a3c6a..841fb36700 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:97453fcc7d831efe74394980249eb22a4c9eca1ff49270933f6ca22b9dcb546d -size 3777899 +oid sha256:ec409d720c37776aed5a7565969a2ec4447532f249742bbd657e68310a76af56 +size 3764179 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index c2f48bd01d..66672b5b93 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:37577dc3fef9366027b5d958b0df65b083d19a1ed9882dfddf1297052cd9072e -size 668963 +oid sha256:d3e4c5fd5d673d742aa39e565e6b29eecf728709032c1aec73e61bc243aedbad +size 662338 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 2821a782f3..45d9167e7b 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:721ab58f8b60909c5c9b920f4fa4bd2e379595591d44664445ed9a3c68668a9b -size 2820384 +oid sha256:db1cb4c14c3f4b414a2b927efc6919c75ad444e0138296293cc5de5942103e7a +size 2801219 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 80be0eb623..0575fc7fc1 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bd9b184372e7e162c086531b0123be27699f8c67f8ff03460d9f222d942d136c -size 737692 +oid sha256:39ad22e09e8668f2d5590174e1eeb270ed1c76a519e1a32e433580ec9c63a620 +size 730490 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index 1ca5d722cd..2e5270935a 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7d9405247fd21f8a9b5591a17f62f197e92118d08fa24e63df6162978b0daec5 -size 3941953 +oid sha256:e784527f13079c936cd53a9e8fe17ccefb9b3e6343ea11bd415e5e2961f36a78 +size 3920330 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index e2bf84df5e..cbc23bf0ba 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ad8a7d5a2c56a1069dc2a5666ac6ef68cb4546e437d6a48bfa9950e04c345df9 -size 659846 +oid sha256:ab60981936f68ff4cabee9d1c990bef674133461457119eab412c8a5ac0ca924 +size 652103 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index 94c0da6413..507e05c711 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bab39b1e4fcc01a038e37744127b1b2a33713cefaf453e71b372533f89d7f0a9 -size 2714831 +oid sha256:7a6e74bf6858d5a227f66419e6071d94a17d2f43447f8769bdd3b487ae77703d +size 2688859 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 85703c5bb3..82f00c2ea1 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4fa79a9b69437445aba35386dd72502e6d6ad3644d73b3e38c8f39e27dce5818 -size 727408 +oid sha256:56173537ae1ac887d684b0098f5ec52b1555dbc19e418ad69ec8ea6591deaf7e +size 721790 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index 8561ef0b59..880f338a9c 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5cc9f9f82a3ed49fdbe7c14f1f763fcfc95c5e441ebb1a045a19a6096cbf5d56 -size 1407863 +oid sha256:9b24ae0331b7cd46063cdfc4c1896d812ab10286bcacc55025bff19b9a5fdcb0 +size 1401645 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index 624819822a..25d9eff42d 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1b266a7e9adde740ca1f02eefe25b71173d192e25c955da11c6212aeb2bcd6d9 -size 989346 +oid sha256:f060876eb33b334218ab044314cfa27c1d537b43fc731659aa3bf0a304b9f9b4 +size 981247 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index 3c722f3a19..f7db8a3e0e 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:08b2cbc76c01790d9c0a21d7b3537651c8c9e1ee6c8c47e4da3758225bd1e1b2 -size 3795623 +oid sha256:ca0ec7ddafea9f3623480b1a7a7e9c1f7bdac3f820111561734b96b15301a1f5 +size 3783410 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index 5dcebc769b..24750c393f 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1eb571876358aca456c0ebc06c60878839acb453f67c44305fc479a126033a96 -size 670306 +oid sha256:ed832ead33a2acde01e6d48791ae4bc72f155148a148414017ac57ac1efc2973 +size 663854 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index fd6543fe47..a64b2130ae 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9d73ce1c4b5abf8458e657fb89a05cad48f5e728d3ac79c09965a785b0b262aa -size 2823777 +oid sha256:5ea229a64db097076d8252eeecda8cc1cfb24899e7f2cbca11ee8186e8e41238 +size 2805472 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index fa9125c99e..c93e52dd15 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fa02977483ccbf2b30fcbef20f8f46900fd0dfb52c5c192d598843e2d1e81451 -size 737847 +oid sha256:1550df52bd55072f947e1b75665bb82df83f5423f337b970ff83d02fb38d4266 +size 731366 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 8dc4fcb67f..806f45467c 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9dad47d23e9f672f6413306857af8dde6bc4550ac93ccf15e001f9e39bd0d207 -size 3945381 +oid sha256:ff53411b3c4014df5304c7159b9fa3fbb468347c9dfe88ad6079bea831284fbb +size 3926286 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index 682f59b863..b76f4462d1 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3a53b4e6f826a41a669818649d54797d21192137dcc69ab5213ddd2826bdad3d -size 660682 +oid sha256:a704288432a8190d4ac11260175d732dfb1c7673b6000c80ddd943f8ded1a63a +size 653704 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index 0f0c183dfa..d136902a06 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:81ff00007e640de85c490c6fb325661b11a48f2fa9b68f61cb7afd2b5271abae -size 2719190 +oid sha256:d580edd46c68d7ba019ab94566a2aff4299e1ce88f8282e35a84c9fb1bd6dd33 +size 2694129 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index 81cb284ac3..96e5d5e94a 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:29eb546287c335a843a19a744191a48a92dd6e02665b1479cead85696b134f30 -size 753677 +oid sha256:700db0829e85f30f9d8140c4fd01b7cb574db5a81aa2c1667d25c5601ebf6602 +size 747895 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index 4334036c7f..a0ae380b5d 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cbc8dd9057e03fca80e9bbdb7d97af6accabacadecb223c4c9797f5509a5928c -size 1467986 +oid sha256:183142c46befd248c7357bee7f209c8312eb912b0fc34e15b9e1508a1fd030bb +size 1460274 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index 3f4390cc7f..758a4eed65 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1b6fae1ff091b382e2d72a90353f5753140581d46d1203e7306a1ed406f329d0 -size 1023930 +oid sha256:ea67d7fa14054078b5768496c4e3af0f699e398d998b09d41dc9081df60571a1 +size 1015493 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index c8b5401b87..e98112a77b 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:58c3bbbb27c284b351d1d4e95bc28c8239b21b917f85bb4c950f4ef9c1c4f789 -size 3931163 +oid sha256:ff7295948137c918b8ca2c8aa262b216a7ed628bf49b86eddb885f4ae2b9da96 +size 3915750 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index 52fd19a50f..0c3313ffa7 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3c9ce2d1ba688153d12942af1a645339105a326f21d8f389f0ecb32e0ecd0452 -size 690187 +oid sha256:90c2f3e9a3db82bae46cdfd9b748e4d80dd79fccf3bd871b3241e499a88269e4 +size 685026 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index 5258048642..99443d09f8 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c79d0117f101aef7812c20adb49fbe15430f18ed806c1321a131afe697ad57f6 -size 2927889 +oid sha256:f1d53e967c9b4648c270cff755fd3b1d48e0f230f74f0c51897274412d99c313 +size 2912087 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index 2246831163..27a753e43f 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e44d3997c28600a5ee1f1366f1e587af0951add2c60977eaaeb91ffc14700e79 -size 760866 +oid sha256:39ef672933bb9a82dcd2ed3542d88cf465468969df5c843689afde1768c90c15 +size 754326 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index cd9f04e2d8..4864a84a6f 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ab94b9a2ee264e027b3d1e9f3e3a87aae1a1dd0086e5afe664fbffed47bb1622 -size 4090364 +oid sha256:96a6ac2720eaf17d88f80e7e41243e10db67e9830f997e3e62e742c6e0e9c7f1 +size 4068858 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 05ae1d10f1..730fc0a123 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1917c5683c658c895bc1d31b2856fdc73facd43233d5d0ae37cee71f66bdeac0 -size 682872 +oid sha256:0036b07a08ad3c89201ee5695fc5a6359904fb604cc0968904657f735f47c6e0 +size 674390 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 473ff8659a..acc3fd621f 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:419c4861567136b7fc45ad73842a57c3586d180a76c476de6c60d523a7157c46 -size 2819926 +oid sha256:f1962684b5d478833474b6b31bf59a55f62fd520126263be8831871c4ba35167 +size 2791064 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index a0a89111bd..7a6e9610dc 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e0e6042dd1b0ed1a65bd2adb1780ce3e416f105f08fee7d52aefb2fd5dab59b8 -size 928441 +oid sha256:49fa8fa465e2280596b481fea4854453fbdf0cc02dd2fa4f655ffca741104d80 +size 920075 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 02cbd809a9..b6026f263a 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f00feebe4ac96473ffb7ad1798d501084f358fa12b21cd5feced7998267fe09b -size 1454908 +oid sha256:9ba80aa376658eed60a8a910dddb82d30d673be20aef40587d60e570799d48a5 +size 1445932 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 56e0b6edfb..d606b78977 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:33cc19b80cff65517197020cfb0947cfd9db16a0d099c11269eb7514d320e4b0 -size 1252037 +oid sha256:1c282a4ac1c7080dfba74a8daacb5248c476d8bef8b9df847185a972c79b0de1 +size 1243609 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 1bd907c4ca..3f2176bff4 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1a5e9698ebf64c3c1fe7560b7c4db6025dc02a97bd0097f140abe9bd4c087f26 -size 4522806 +oid sha256:0f78f84bef5c440b5b6566e39bd3936f28923a74ef70834a093c0ae7c60a4e0f +size 4507331 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index d51e908aa0..9cb9ece979 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e7a292c5c441fbe5c75dbbf48aa9b4a2ec010e45e1460230f5fea7e71ca01e37 -size 833689 +oid sha256:796062e32d5be780bfb12e134b703791f58a8a05854288b4629379e1fd470965 +size 826073 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index b9a2a096c5..6b634bfc7f 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b31e5ef6356f9865da88d0692e8afd2109ff4fc89fec631389bc7ab348ff67ba -size 3333239 +oid sha256:c82a9926e69b8a5c4876576325f024aee7c0c49b690bf8ab30056a7f40308b3f +size 3314262 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index f8fc09c6ac..e2b2161c36 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5ec60fd1e9640d1221453ad598bab9e95b52c4c0ce4accd0a24b22b5f6c6f99b -size 932743 +oid sha256:115a943b5798e8bcf00bbc7cef687cfd3cca893ced538b14b06aab181f851fa8 +size 923249 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index f72e347ea1..827d117771 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b35a450990236df60dc0434042b90ab2bd2ecfe0bd8d2e032bb583393d0b0d23 -size 4763020 +oid sha256:d15668c27a50b033ee3d69cdb707bd1ec3d8541911a0128a66e26154cebbb775 +size 4739242 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index 32438a7324..1ab1b18f1c 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cf708bded4b8a6729a6268c300d078ece4c82af0c23be6160c3ffa5c60c78e3b -size 822545 +oid sha256:d147496b0841f77f725a28ffda175d9da5be5d8c953bec8f89a80927631c4204 +size 814245 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 86b3591708..bec6564c81 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ff700b14c2bf330c49af9bb6a961cea7b93d80fa68812ec6c9406cfd460846d8 -size 3225198 +oid sha256:17bbfe27163bf14bec1d266052dde86b69da479003c5785e190006b8382fbb90 +size 3193477 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 1261bd4501..17ad132a21 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7d4b3a8d4983b45f8694bd6986d544f7dc81c76a4c2edb04be25c7ae305410d7 -size 567063 +oid sha256:2238ce357ed2f597e5915f5d9cdb5ef4cd5eb01067b8503b1446a5e86c6bfe12 +size 562202 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 01ff846606..b06228f56c 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4ddbb163e38d61db50edd755776da45f8d19a951f08c16feb9f9ac050bf18edf -size 1043194 +oid sha256:a33d968fbb779416b8a3b6ff0803bbcd39e82a0f70b4694516227698c5693ff7 +size 1038672 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index 27e1487600..b8c5960fd4 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c01f114c557d789936033b2628213bd875c2bae7c04c1a1836195744f51d4f37 -size 780600 +oid sha256:0e33eac452c933f0c5e64161f50d029747031092b387c4d610463346a0ea9627 +size 777559 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 150446506f..96b0afdf41 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:34fe783f59565f4bcda5e382ba4dab39bedce438828697b046e0828d20ac8cf9 -size 2956675 +oid sha256:a3693438e6521a69e147285b2863aae2ab3f734a2e527a639c8e9e942d497981 +size 2953034 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 1f550424be..6485550193 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1ed3f204603a5c4f78cba91a084250b807bc44cb1f17b8c42514f1c5038e98a9 -size 527100 +oid sha256:83bea77fd58eec4af3830f23218f5804d2a6a241643f2d5f08311ca37b950104 +size 523372 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index f894fb4992..404c0392ab 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:838f4199923c66f873342e085c1c10cfbf2c9a2d32b5d9e185adacdb437889fc -size 2134882 +oid sha256:c8b13b273adb13c6aa9824f4c32c032140db78b9f8967db3f424cfef2092df31 +size 2128714 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index daaec802c5..82b7511227 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06687592719970d4ca1b639ee44eedf155f02e9eac54eb1f9d9fd7daae22a2b3 -size 577341 +oid sha256:38aaad5ed30aca927cebf447cf8814cf7a4a0211f9ab3c64d54db583b2cb85bb +size 572837 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index dfaf036ebe..622c00df42 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8aaaffc82a79aac3cc876986d1e17b91300c5c5432a403ec9357e580f83be78e -size 2953720 +oid sha256:072efb85cd4e6ee86fda5795ce24145ea51e036d1ae094494556cf21dba19a44 +size 2946405 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 43425d371a..9cf0c6aa99 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:36c86dc380a62ad99a7982d0980bf7e60e97164bf21399fae43b574b6f23a1bd -size 519125 +oid sha256:6e89f7d741b82886db65dc459de4e10f2a8a51acdf0756d365f9d5033e3d7e65 +size 515958 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index dcb245c078..3774c2416f 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:263b658414f063a5fb472824f39e0fc73b3d0964b3855280010e734d1b768767 -size 2039269 +oid sha256:bf70999ee1a4ba0eaf69e7db18d0a5e518a52c68a5cc2a006689fcb3ffef9b77 +size 2024814 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index bcd904cd7c..d1dc9f7cec 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c2c5b99f2d1cd187f44385ce3c3b159f9e4e365172286b8e6de471b9c225c948 -size 876339 +oid sha256:c0db01867c96762c75b9fcc5d487c43283967ac1915c5a0e9143b395d8990822 +size 867732 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 0e5c87bbfc..24511d23d4 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1a89503f2d199c66b2f88cf3e33c947184b9c3a78fa2dcadcecd37240ac6a2d2 -size 1549197 +oid sha256:045aa33b2b47f8577f5699c98a3ed3b64cb0ab70b52ad5d0ad6c6ef1c461c710 +size 1540598 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index 869bda44e6..44d2b35ec1 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bf587adf7d0d1b6afb2935eaa6535579cdf13ebbb5f8688518ac4d19d154702f -size 1164295 +oid sha256:4a2f0d0409392686e8096227b397ba2be89ea8f4a745096c950c9f8b4940cb04 +size 1153735 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index 271bc486ba..08e64c1643 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7231746844094844703e940c4e000deb09ae7af012e1a42d6f8b812f8ebb33d8 -size 4440062 +oid sha256:b1427aec856e1a33df6f7c3404b671cb88a808e7fce1460d046556c375028ded +size 4424329 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index db200d95cc..395b85329e 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5376c55b5b4766f63fb41e50409a7d883a0381cf9b3ec5f204c19e47bdf95c70 -size 808373 +oid sha256:b0f3eedae36c3928008b314116b0028568f3107b59c88261e973adc33bd7c29e +size 799626 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index d5b47be48c..b54c003865 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f37dddf49df2b84b31df5e25c14e5b0e9a7575a98cbc014b0dd6ad389e32f1d7 -size 3391824 +oid sha256:6d3899c535ab32a0cf941e9884027e9675fe631c0bc3c04c08879e578561845b +size 3366500 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index bfce9fd8c5..cdb8c5de40 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:04ccfdc9cba8dad7c633fd41df16c636422fd3d2332a91d47b385bd575053ee0 -size 884982 +oid sha256:d0e096a9b96403b361e59429ecf5743ce7f119213dd169678c1553cab387ad05 +size 875038 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index ef13dff257..d298326b16 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dc342e47ff36caf7fb5d43f27d1eac52709453a90c9c8469dc4da6447fba7fa5 -size 4743824 +oid sha256:7217928ab86e0efb3a3e38254797458af36569dc5de0cbdaf5e0a3d281f24fd2 +size 4720970 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index c79d28c435..01d2192fe2 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2ded52b4ac81ba39e60af9a59679872fd9cb5b38317ef356eca978a7ae725fd5 -size 796014 +oid sha256:427307bc0a1a1b4a877013aa6005a36d000ece79c809909cf558e2b13a42bd95 +size 787794 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 9ba1db69a2..e97ce27026 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3591e3232239178ca55a380ba6169406d9b6bbe1e477844aacc19a438ad62944 -size 3274151 +oid sha256:c810147b62b3a8adccf8e191bb417db938bb0e2e609ee86c01305ea941bdfbd4 +size 3244055 diff --git a/middleware/cache-full-rendering.js b/middleware/cache-full-rendering.js new file mode 100644 index 0000000000..cf64cc8b88 --- /dev/null +++ b/middleware/cache-full-rendering.js @@ -0,0 +1,171 @@ +import zlib from 'zlib' + +import cheerio from 'cheerio' +import QuickLRU from 'quick-lru' + +// This is what NextJS uses when it injects the JSON serialized +// in the ` + // + const primerData = $('script#__PRIMER_DATA__') + console.assert(primerData.length === 1, 'Not exactly 1') + const parsedPrimerData = JSON.parse(primerData.get()[0].children[0].data) + parsedPrimerData.resolvedServerColorMode = cssTheme.colorMode === 'dark' ? 'night' : 'day' + primerData.text(htmlEscapeJsonString(JSON.stringify(parsedPrimerData))) +} diff --git a/middleware/detect-language.js b/middleware/detect-language.js index 9472e8d36c..822e317f45 100644 --- a/middleware/detect-language.js +++ b/middleware/detect-language.js @@ -48,13 +48,17 @@ export function getLanguageCodeFromPath(path) { return languageKeys.includes(maybeLanguage) ? maybeLanguage : 'en' } +export function getLanguageCodeFromHeader(req) { + const browserLanguages = parser.parse(req.headers['accept-language']) + return getUserLanguage(browserLanguages) +} + export default function detectLanguage(req, res, next) { req.language = getLanguageCodeFromPath(req.path) // Detecting browser language by user preference req.userLanguage = getUserLanguageFromCookie(req) if (!req.userLanguage) { - const browserLanguages = parser.parse(req.headers['accept-language']) - req.userLanguage = getUserLanguage(browserLanguages) + req.userLanguage = getLanguageCodeFromHeader(req) } return next() } diff --git a/middleware/fast-root-redirect.js b/middleware/fast-root-redirect.js new file mode 100644 index 0000000000..a699011119 --- /dev/null +++ b/middleware/fast-root-redirect.js @@ -0,0 +1,15 @@ +import { cacheControlFactory } from './cache-control.js' +import { PREFERRED_LOCALE_COOKIE_NAME, getLanguageCodeFromHeader } from './detect-language.js' + +const cacheControl = cacheControlFactory(0) + +export default function fastRootRedirect(req, res, next) { + if (!req.headers.cookie || !req.headers.cookie.includes(PREFERRED_LOCALE_COOKIE_NAME)) { + // No preferred language cookie header! + const language = getLanguageCodeFromHeader(req) || 'en' + cacheControl(res) + res.set('location', `/${language}`) + return res.status(302).send('') + } + next() +} diff --git a/middleware/index.js b/middleware/index.js index 2767f8d4bb..213ccf376f 100644 --- a/middleware/index.js +++ b/middleware/index.js @@ -63,10 +63,11 @@ import assetPreprocessing from './asset-preprocessing.js' import archivedAssetRedirects from './archived-asset-redirects.js' import favicons from './favicons.js' import setStaticAssetCaching from './static-asset-caching.js' +import cacheFullRendering from './cache-full-rendering.js' import protect from './overload-protection.js' import fastHead from './fast-head.js' - import fastlyCacheTest from './fastly-cache-test.js' +import fastRootRedirect from './fast-root-redirect.js' const { DEPLOYMENT_ENV, NODE_ENV } = process.env const isDevelopment = NODE_ENV === 'development' @@ -239,6 +240,7 @@ export default function (app) { } // *** Early exits *** + app.get('/', fastRootRedirect) app.use(instrument(handleInvalidPaths, './handle-invalid-paths')) app.use(asyncMiddleware(instrument(handleNextDataPath, './handle-next-data-path'))) @@ -317,6 +319,10 @@ export default function (app) { // full page rendering. app.head('/*', fastHead) + // For performance, this is before contextualizers if, on a cache hit, + // we can't reuse a rendered response without having to contextualize. + app.get('/*', asyncMiddleware(instrument(cacheFullRendering, './cache-full-rendering'))) + // *** Preparation for render-page: contextualizers *** app.use(asyncMiddleware(instrument(releaseNotes, './contextualizers/release-notes'))) app.use(instrument(graphQL, './contextualizers/graphql')) diff --git a/middleware/overload-protection.js b/middleware/overload-protection.js index a596fdee3c..6e089ec38a 100644 --- a/middleware/overload-protection.js +++ b/middleware/overload-protection.js @@ -1,7 +1,7 @@ import overloadProtection from 'overload-protection' // Default is 42. We're being more conservative. -const DEFAULT_MAX_DELAY_DEFAULT = 300 +const DEFAULT_MAX_DELAY_DEFAULT = 500 const OVERLOAD_PROTECTION_MAX_DELAY = parseInt( process.env.OVERLOAD_PROTECTION_MAX_DELAY || DEFAULT_MAX_DELAY_DEFAULT, diff --git a/middleware/render-page.js b/middleware/render-page.js index 36919a5ed8..f24a2cdf67 100644 --- a/middleware/render-page.js +++ b/middleware/render-page.js @@ -67,7 +67,7 @@ export default async function renderPage(req, res, next) { // Just finish fast without all the details like Content-Length if (req.method === 'HEAD') { - return res.status(200).end() + return res.status(200).send('') } // Updating the Last-Modified header for substantive changes on a page for engineering diff --git a/next.config.js b/next.config.js index c2a44f89d8..9ab2fa2ff0 100644 --- a/next.config.js +++ b/next.config.js @@ -39,4 +39,7 @@ module.exports = { config.experiments.topLevelAwait = true return config }, + + // https://nextjs.org/docs/api-reference/next.config.js/compression + compress: false, } diff --git a/package-lock.json b/package-lock.json index 3337f44814..b65201b8f7 100644 --- a/package-lock.json +++ b/package-lock.json @@ -60,6 +60,7 @@ "overload-protection": "^1.2.3", "parse5": "^6.0.1", "port-used": "^2.0.8", + "quick-lru": "6.1.0", "react": "^17.0.2", "react-dom": "^17.0.2", "react-markdown": "^8.0.0", @@ -4100,48 +4101,6 @@ "once": "^1.4.0" } }, - "node_modules/@octokit/request/node_modules/node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "dev": true, - "dependencies": { - "whatwg-url": "^5.0.0" - }, - "engines": { - "node": "4.x || >=6.0.0" - }, - "peerDependencies": { - "encoding": "^0.1.0" - }, - "peerDependenciesMeta": { - "encoding": { - "optional": true - } - } - }, - "node_modules/@octokit/request/node_modules/tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "dev": true - }, - "node_modules/@octokit/request/node_modules/webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "dev": true - }, - "node_modules/@octokit/request/node_modules/whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "dev": true, - "dependencies": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - }, "node_modules/@octokit/rest": { "version": "18.12.0", "resolved": "https://registry.npmjs.org/@octokit/rest/-/rest-18.12.0.tgz", @@ -4786,9 +4745,9 @@ "devOptional": true }, "node_modules/@types/yauzl": { - "version": "2.9.2", - "resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.9.2.tgz", - "integrity": "sha512-8uALY5LTvSuHgloDVUvWP3pIauILm+8/0pDMokuDYIoNsOkSwd5AiHBTSEJjKTDcZr5z8UpgOWZkxBF4iJftoA==", + "version": "2.10.0", + "resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.10.0.tgz", + "integrity": "sha512-Cn6WYCm0tXv8p6k+A8PvbDG763EDpBoTzHdA+Q/MF6H3sapGjCm9NzoaJncJS9tUKSuCoDs9XHxYYsQDgxR6kw==", "optional": true, "dependencies": { "@types/node": "*" @@ -5274,7 +5233,7 @@ "node_modules/array-uniq": { "version": "1.0.3", "resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.3.tgz", - "integrity": "sha1-r2rId6Jcx/dOBYiUdThY39sk/bY=", + "integrity": "sha512-MNha4BWQ6JbwhFhj03YK552f7cb3AzoE8SzeljgChvL1dl3IcvggXVz1DilzySZkCja+CXuZbdW7yATchWn8/Q==", "optional": true, "engines": { "node": ">=0.10.0" @@ -6420,7 +6379,7 @@ "node_modules/bfj": { "version": "4.2.4", "resolved": "https://registry.npmjs.org/bfj/-/bfj-4.2.4.tgz", - "integrity": "sha1-hfeyNoPCr9wVhgOEotHD+sgO0zo=", + "integrity": "sha512-+c08z3TYqv4dy9b0MAchQsxYlzX9D2asHWW4VhO4ZFTnK7v9ps6iNhEQLqJyEZS6x9G0pgOCk/L7B9E4kp8glQ==", "optional": true, "dependencies": { "check-types": "^7.3.0", @@ -6467,7 +6426,7 @@ "node_modules/bmp-js": { "version": "0.1.0", "resolved": "https://registry.npmjs.org/bmp-js/-/bmp-js-0.1.0.tgz", - "integrity": "sha1-4Fpj95amwf8l9Hcex62twUjAcjM=", + "integrity": "sha512-vHdS19CnY3hwiNdkaqk93DvjVLfbEcI8mys4UjuWrlX1haDmroo8o4xCzh4wD6DGV6HxRCyauwhHRqMTfERtjw==", "optional": true }, "node_modules/bn.js": { @@ -6792,7 +6751,7 @@ "node_modules/buffer-crc32": { "version": "0.2.13", "resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz", - "integrity": "sha1-DTM+PwDqxQqhRUq9MO+MKl2ackI=", + "integrity": "sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==", "optional": true, "engines": { "node": "*" @@ -6801,7 +6760,7 @@ "node_modules/buffer-equal": { "version": "0.0.1", "resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-0.0.1.tgz", - "integrity": "sha1-kbx0sR6kBbyRa8aqkI+q+ltKrEs=", + "integrity": "sha512-RgSV6InVQ9ODPdLWJ5UAqBqJBOg370Nz6ZQtRzpt6nUjc8v0St97uJ4PYC6NztqIScrAXafKM3mZPMygSe1ggA==", "optional": true, "engines": { "node": ">=0.4.0" @@ -6928,6 +6887,18 @@ "url": "https://github.com/sponsors/sindresorhus" } }, + "node_modules/camelcase-keys/node_modules/quick-lru": { + "version": "5.1.1", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", + "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==", + "dev": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, "node_modules/camelcase-keys/node_modules/type-fest": { "version": "1.4.0", "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz", @@ -8745,16 +8716,6 @@ "node": ">= 0.8.0" } }, - "node_modules/escodegen/node_modules/source-map": { - "version": "0.6.1", - "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz", - "integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==", - "dev": true, - "optional": true, - "engines": { - "node": ">=0.10.0" - } - }, "node_modules/escodegen/node_modules/type-check": { "version": "0.3.2", "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz", @@ -10221,9 +10182,9 @@ } }, "node_modules/fs-extra": { - "version": "10.0.1", - "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.0.1.tgz", - "integrity": "sha512-NbdoVMZso2Lsrn/QwLXOy6rm0ufY2zEOKCDzJR/0kBsb0E6qed0P3iYK+Ath3BfvXEeu4JhEtXLgILx5psUfag==", + "version": "10.1.0", + "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.1.0.tgz", + "integrity": "sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==", "optional": true, "dependencies": { "graceful-fs": "^4.2.0", @@ -10249,19 +10210,6 @@ "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", "devOptional": true }, - "node_modules/fsevents": { - "version": "2.3.2", - "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz", - "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==", - "hasInstallScript": true, - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^8.16.0 || ^10.6.0 || >=11.0.0" - } - }, "node_modules/function-bind": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz", @@ -10289,48 +10237,6 @@ "node": ">=10" } }, - "node_modules/gaxios/node_modules/node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "dev": true, - "dependencies": { - "whatwg-url": "^5.0.0" - }, - "engines": { - "node": "4.x || >=6.0.0" - }, - "peerDependencies": { - "encoding": "^0.1.0" - }, - "peerDependenciesMeta": { - "encoding": { - "optional": true - } - } - }, - "node_modules/gaxios/node_modules/tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "dev": true - }, - "node_modules/gaxios/node_modules/webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "dev": true - }, - "node_modules/gaxios/node_modules/whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "dev": true, - "dependencies": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - }, "node_modules/gemoji": { "version": "4.2.1", "resolved": "https://registry.npmjs.org/gemoji/-/gemoji-4.2.1.tgz", @@ -10419,12 +10325,12 @@ "dev": true }, "node_modules/gifwrap": { - "version": "0.9.2", - "resolved": "https://registry.npmjs.org/gifwrap/-/gifwrap-0.9.2.tgz", - "integrity": "sha512-fcIswrPaiCDAyO8xnWvHSZdWChjKXUanKKpAiWWJ/UTkEi/aYKn5+90e7DE820zbEaVR9CE2y4z9bzhQijZ0BA==", + "version": "0.9.4", + "resolved": "https://registry.npmjs.org/gifwrap/-/gifwrap-0.9.4.tgz", + "integrity": "sha512-MDMwbhASQuVeD4JKd1fKgNgCRL3fGqMM4WaqpNhWO0JiMOAjbQdumbs4BbBZEy9/M00EHEjKN3HieVhCUlwjeQ==", "optional": true, "dependencies": { - "image-q": "^1.1.1", + "image-q": "^4.0.0", "omggif": "^1.0.10" } }, @@ -11367,6 +11273,17 @@ "node": ">=10.19.0" } }, + "node_modules/http2-wrapper/node_modules/quick-lru": { + "version": "5.1.1", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", + "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==", + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, "node_modules/https-browserify": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/https-browserify/-/https-browserify-1.0.0.tgz", @@ -11455,14 +11372,20 @@ "dev": true }, "node_modules/image-q": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/image-q/-/image-q-1.1.1.tgz", - "integrity": "sha1-/IQJlmRGC5DKhi2TALa/u7+/gFY=", + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/image-q/-/image-q-4.0.0.tgz", + "integrity": "sha512-PfJGVgIfKQJuq3s0tTDOKtztksibuUEbJQIYT3by6wctQo+Rdlh7ef4evJ5NCdxY4CfMbvFkocEwbl4BF8RlJw==", "optional": true, - "engines": { - "node": ">=0.9.0" + "dependencies": { + "@types/node": "16.9.1" } }, + "node_modules/image-q/node_modules/@types/node": { + "version": "16.9.1", + "resolved": "https://registry.npmjs.org/@types/node/-/node-16.9.1.tgz", + "integrity": "sha512-QpLcX9ZSsq3YYUUnD3nFDY8H7wctAhQj/TFKL8Ya8v5fMm3CFXxo8zStsLAl780ltoYoo1WvKUVGBQK+1ifr7g==", + "optional": true + }, "node_modules/image-size": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/image-size/-/image-size-1.0.0.tgz", @@ -15761,25 +15684,6 @@ "url": "https://github.com/chalk/supports-color?sponsor=1" } }, - "node_modules/next/node_modules/node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "dependencies": { - "whatwg-url": "^5.0.0" - }, - "engines": { - "node": "4.x || >=6.0.0" - }, - "peerDependencies": { - "encoding": "^0.1.0" - }, - "peerDependenciesMeta": { - "encoding": { - "optional": true - } - } - }, "node_modules/next/node_modules/node-releases": { "version": "1.1.77", "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-1.1.77.tgz", @@ -15843,11 +15747,6 @@ "node": ">=4" } }, - "node_modules/next/node_modules/tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=" - }, "node_modules/next/node_modules/watchpack": { "version": "2.1.1", "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.1.1.tgz", @@ -15860,20 +15759,6 @@ "node": ">=10.13.0" } }, - "node_modules/next/node_modules/webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=" - }, - "node_modules/next/node_modules/whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "dependencies": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - }, "node_modules/no-case": { "version": "3.0.4", "resolved": "https://registry.npmjs.org/no-case/-/no-case-3.0.4.tgz", @@ -15899,6 +15784,44 @@ "node": ">= 10.13" } }, + "node_modules/node-fetch": { + "version": "2.6.7", + "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", + "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", + "dependencies": { + "whatwg-url": "^5.0.0" + }, + "engines": { + "node": "4.x || >=6.0.0" + }, + "peerDependencies": { + "encoding": "^0.1.0" + }, + "peerDependenciesMeta": { + "encoding": { + "optional": true + } + } + }, + "node_modules/node-fetch/node_modules/tr46": { + "version": "0.0.3", + "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", + "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=" + }, + "node_modules/node-fetch/node_modules/webidl-conversions": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", + "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=" + }, + "node_modules/node-fetch/node_modules/whatwg-url": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", + "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", + "dependencies": { + "tr46": "~0.0.3", + "webidl-conversions": "^3.0.0" + } + }, "node_modules/node-html-parser": { "version": "1.4.9", "resolved": "https://registry.npmjs.org/node-html-parser/-/node-html-parser-1.4.9.tgz", @@ -16669,7 +16592,7 @@ "node_modules/pa11y-ci/node_modules/ansi-regex": { "version": "2.1.1", "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.1.1.tgz", - "integrity": "sha1-w7M6te42DYbg5ijwRorn7yfWVN8=", + "integrity": "sha512-TIGnTpdo+E3+pCyAluZvtED5p5wCqLdezCyhPZzKPcxvFplEt4i+W7OONCKgeZFT3+y5NZZfOOS/Bdcanm1MYA==", "optional": true, "engines": { "node": ">=0.10.0" @@ -16678,7 +16601,7 @@ "node_modules/pa11y-ci/node_modules/ansi-styles": { "version": "2.2.1", "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.2.1.tgz", - "integrity": "sha1-tDLdM1i2NM914eRmQ2gkBTPB3b4=", + "integrity": "sha512-kmCevFghRiWM7HB5zTPULl4r9bVFSWjz62MhqizDGUrq2NWuNMQyuv4tHHoKJHs69M/MF64lEcHdYIocrdWQYA==", "optional": true, "engines": { "node": ">=0.10.0" @@ -16687,7 +16610,7 @@ "node_modules/pa11y-ci/node_modules/array-union": { "version": "1.0.2", "resolved": "https://registry.npmjs.org/array-union/-/array-union-1.0.2.tgz", - "integrity": "sha1-mjRBDk9OPaI96jdb5b5w8kd47Dk=", + "integrity": "sha512-Dxr6QJj/RdU/hCaBjOfxW+q6lyuVE6JFWIrAUpuOOhoJJoQ99cUn3igRaHVB5P9WrgFVN0FfArM3x0cueOU8ng==", "optional": true, "dependencies": { "array-uniq": "^1.0.1" @@ -16709,7 +16632,7 @@ "node_modules/pa11y-ci/node_modules/chalk": { "version": "1.1.3", "resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.3.tgz", - "integrity": "sha1-qBFcVeSnAv5NFQq9OHKCKn4J/Jg=", + "integrity": "sha512-U3lRVLMSlsCfjqYPbLyVv11M9CPW4I728d6TCKMAOJueEeB9/8o+eSsMnxPJD+Q+K909sdESg7C+tIkoH6on1A==", "optional": true, "dependencies": { "ansi-styles": "^2.2.1", @@ -16768,15 +16691,15 @@ "optional": true }, "node_modules/pa11y-ci/node_modules/glob": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz", - "integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==", + "version": "7.2.3", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz", + "integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==", "optional": true, "dependencies": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", "inherits": "2", - "minimatch": "^3.0.4", + "minimatch": "^3.1.1", "once": "^1.3.0", "path-is-absolute": "^1.0.0" }, @@ -16849,30 +16772,11 @@ "mkdirp": "bin/cmd.js" } }, - "node_modules/pa11y-ci/node_modules/node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "optional": true, - "dependencies": { - "whatwg-url": "^5.0.0" - }, - "engines": { - "node": "4.x || >=6.0.0" - }, - "peerDependencies": { - "encoding": "^0.1.0" - }, - "peerDependenciesMeta": { - "encoding": { - "optional": true - } - } - }, "node_modules/pa11y-ci/node_modules/puppeteer": { "version": "1.19.0", "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-1.19.0.tgz", "integrity": "sha512-2S6E6ygpoqcECaagDbBopoSOPDv0pAZvTbnBgUY+6hq0/XDFDOLEMNlHF/SKJlzcaZ9ckiKjKDuueWI3FN/WXw==", + "deprecated": "Version no longer supported. Upgrade to @latest", "hasInstallScript": true, "optional": true, "dependencies": { @@ -16922,28 +16826,6 @@ "node": ">=0.8.0" } }, - "node_modules/pa11y-ci/node_modules/tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "optional": true - }, - "node_modules/pa11y-ci/node_modules/webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "optional": true - }, - "node_modules/pa11y-ci/node_modules/whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "optional": true, - "dependencies": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - }, "node_modules/pa11y-ci/node_modules/ws": { "version": "6.2.2", "resolved": "https://registry.npmjs.org/ws/-/ws-6.2.2.tgz", @@ -16957,6 +16839,7 @@ "version": "1.0.1", "resolved": "https://registry.npmjs.org/pa11y-reporter-cli/-/pa11y-reporter-cli-1.0.1.tgz", "integrity": "sha512-k+XPl5pBU2R1J6iagGv/GpN/dP7z2cX9WXqO0ALpBwHlHN3ZSukcHCOhuLMmkOZNvufwsvobaF5mnaZxT70YyA==", + "deprecated": "This package is now bundled with pa11y. You can find the latest version of this package in the pa11y repo.", "optional": true, "dependencies": { "chalk": "^2.1.0" @@ -17040,6 +16923,7 @@ "version": "1.0.0", "resolved": "https://registry.npmjs.org/pa11y-reporter-csv/-/pa11y-reporter-csv-1.0.0.tgz", "integrity": "sha512-S2gFgbAvONBzAVsVbF8zsYabszrzj7SKhQxrEbw19zF0OFI8wCWn8dFywujYYkg674rmyjweSxSdD+kHTcx4qA==", + "deprecated": "This package is now bundled with pa11y. You can find the latest version of this package in the pa11y repo.", "optional": true, "engines": { "node": ">=8" @@ -17049,6 +16933,7 @@ "version": "1.0.0", "resolved": "https://registry.npmjs.org/pa11y-reporter-json/-/pa11y-reporter-json-1.0.0.tgz", "integrity": "sha512-EdLrzh1hyZ8DudCSSrcakgtsHDiSsYNsWLSoEAo1JnFTIK8hYpD7vL+xgd0u+LXDxz9wLLFnckdubpklaRpl/w==", + "deprecated": "This package is now bundled with pa11y. You can find the latest version of this package in the pa11y repo.", "optional": true, "dependencies": { "bfj": "^4.2.3" @@ -17061,6 +16946,7 @@ "version": "1.0.2", "resolved": "https://registry.npmjs.org/pa11y-runner-axe/-/pa11y-runner-axe-1.0.2.tgz", "integrity": "sha512-HMw5kQZz16vS5Bhe067esgeuULNzFYP4ixOFAHxOurwGDptlyc2OqH6zfUuK4szB9tbgb5F23v3qz9hCbkGRpw==", + "deprecated": "This package is now bundled with pa11y. You can find the latest version of this package in the pa11y repo.", "optional": true, "dependencies": { "axe-core": "^3.5.1" @@ -17082,6 +16968,7 @@ "version": "1.2.1", "resolved": "https://registry.npmjs.org/pa11y-runner-htmlcs/-/pa11y-runner-htmlcs-1.2.1.tgz", "integrity": "sha512-flatSp6moEbqzny18b2IEoDXEWj6xJbJrszdBjUAPQBCN11QRW+SZ0U4uFnxNTLPpXs30N/a9IlH4vYiRr2nPg==", + "deprecated": "This package is now bundled with pa11y. You can find the latest version of this package in the pa11y repo.", "optional": true, "dependencies": { "html_codesniffer": "~2.4.1" @@ -17149,15 +17036,15 @@ "optional": true }, "node_modules/pa11y/node_modules/glob": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz", - "integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==", + "version": "7.2.3", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz", + "integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==", "optional": true, "dependencies": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", "inherits": "2", - "minimatch": "^3.0.4", + "minimatch": "^3.1.1", "once": "^1.3.0", "path-is-absolute": "^1.0.0" }, @@ -17218,6 +17105,7 @@ "version": "1.19.0", "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-1.19.0.tgz", "integrity": "sha512-2S6E6ygpoqcECaagDbBopoSOPDv0pAZvTbnBgUY+6hq0/XDFDOLEMNlHF/SKJlzcaZ9ckiKjKDuueWI3FN/WXw==", + "deprecated": "Version no longer supported. Upgrade to @latest", "hasInstallScript": true, "optional": true, "dependencies": { @@ -17527,9 +17415,9 @@ } }, "node_modules/parse-headers": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/parse-headers/-/parse-headers-2.0.3.tgz", - "integrity": "sha512-QhhZ+DCCit2Coi2vmAKbq5RGTRcQUOE2+REgv8vdyu7MnYx2eZztegqtTx99TZ86GTIwqiy3+4nQTWZ2tgmdCA==", + "version": "2.0.5", + "resolved": "https://registry.npmjs.org/parse-headers/-/parse-headers-2.0.5.tgz", + "integrity": "sha512-ft3iAoLOB/MlwbNXgzy43SWGP6sQki2jQvAyBg/zDFAgr9bfNWZIUj42Kw2eJIl8kEi4PbgE6U1Zau/HwI75HA==", "optional": true }, "node_modules/parse-json": { @@ -18137,6 +18025,7 @@ "version": "9.1.1", "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-9.1.1.tgz", "integrity": "sha512-W+nOulP2tYd/ZG99WuZC/I5ljjQQ7EUw/jQGcIb9eu8mDlZxNY2SgcJXTLG9h5gRvqA3uJOe4hZXYsd3EqioMw==", + "deprecated": "Version no longer supported. Upgrade to @latest", "hasInstallScript": true, "optional": true, "dependencies": { @@ -18157,48 +18046,6 @@ "node": ">=10.18.1" } }, - "node_modules/puppeteer/node_modules/node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "optional": true, - "dependencies": { - "whatwg-url": "^5.0.0" - }, - "engines": { - "node": "4.x || >=6.0.0" - }, - "peerDependencies": { - "encoding": "^0.1.0" - }, - "peerDependenciesMeta": { - "encoding": { - "optional": true - } - } - }, - "node_modules/puppeteer/node_modules/tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "optional": true - }, - "node_modules/puppeteer/node_modules/webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "optional": true - }, - "node_modules/puppeteer/node_modules/whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "optional": true, - "dependencies": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - }, "node_modules/qs": { "version": "6.9.6", "resolved": "https://registry.npmjs.org/qs/-/qs-6.9.6.tgz", @@ -18256,11 +18103,11 @@ ] }, "node_modules/quick-lru": { - "version": "5.1.1", - "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", - "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==", + "version": "6.1.0", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-6.1.0.tgz", + "integrity": "sha512-8HdyR8c0jNVWbYrhUWs9Tg/qAAHgjuJoOIX+mP3eIhgqPO9ytMRURCEFTkOxaHLLsEXo0Cm+bXO5ULuGez+45g==", "engines": { - "node": ">=10" + "node": ">=12" }, "funding": { "url": "https://github.com/sponsors/sindresorhus" @@ -22474,9 +22321,9 @@ } }, "node_modules/website-scraper/node_modules/got": { - "version": "12.0.3", - "resolved": "https://registry.npmjs.org/got/-/got-12.0.3.tgz", - "integrity": "sha512-hmdcXi/S0gcAtDg4P8j/rM7+j3o1Aq6bXhjxkDhRY2ipe7PHpvx/14DgTY2czHOLaGeU8VRvRecidwfu9qdFug==", + "version": "12.0.4", + "resolved": "https://registry.npmjs.org/got/-/got-12.0.4.tgz", + "integrity": "sha512-2Eyz4iU/ktq7wtMFXxzK7g5p35uNYLLdiZarZ5/Yn3IJlNEpBd5+dCgcAyxN8/8guZLszffwe3wVyw+DEVrpBg==", "optional": true, "dependencies": { "@sindresorhus/is": "^4.6.0", @@ -22501,9 +22348,9 @@ } }, "node_modules/website-scraper/node_modules/http2-wrapper": { - "version": "2.1.10", - "resolved": "https://registry.npmjs.org/http2-wrapper/-/http2-wrapper-2.1.10.tgz", - "integrity": "sha512-QHgsdYkieKp+6JbXP25P+tepqiHYd+FVnDwXpxi/BlUcoIB0nsmTOymTNvETuTO+pDuwcSklPE72VR3DqV+Haw==", + "version": "2.1.11", + "resolved": "https://registry.npmjs.org/http2-wrapper/-/http2-wrapper-2.1.11.tgz", + "integrity": "sha512-aNAk5JzLturWEUiuhAN73Jcbq96R7rTitAoXV54FYMatvihnpD2+6PUgU4ce3D/m5VDbw+F5CsyKSF176ptitQ==", "optional": true, "dependencies": { "quick-lru": "^5.1.1", @@ -22546,6 +22393,18 @@ "node": ">=12.20" } }, + "node_modules/website-scraper/node_modules/quick-lru": { + "version": "5.1.1", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", + "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==", + "optional": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, "node_modules/whatwg-encoding": { "version": "1.0.5", "resolved": "https://registry.npmjs.org/whatwg-encoding/-/whatwg-encoding-1.0.5.tgz", @@ -25836,39 +25695,6 @@ "is-plain-object": "^5.0.0", "node-fetch": "^2.6.1", "universal-user-agent": "^6.0.0" - }, - "dependencies": { - "node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "dev": true, - "requires": { - "whatwg-url": "^5.0.0" - } - }, - "tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "dev": true - }, - "webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "dev": true - }, - "whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "dev": true, - "requires": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - } } }, "@octokit/request-error": { @@ -26491,9 +26317,9 @@ "devOptional": true }, "@types/yauzl": { - "version": "2.9.2", - "resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.9.2.tgz", - "integrity": "sha512-8uALY5LTvSuHgloDVUvWP3pIauILm+8/0pDMokuDYIoNsOkSwd5AiHBTSEJjKTDcZr5z8UpgOWZkxBF4iJftoA==", + "version": "2.10.0", + "resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.10.0.tgz", + "integrity": "sha512-Cn6WYCm0tXv8p6k+A8PvbDG763EDpBoTzHdA+Q/MF6H3sapGjCm9NzoaJncJS9tUKSuCoDs9XHxYYsQDgxR6kw==", "optional": true, "requires": { "@types/node": "*" @@ -26816,7 +26642,7 @@ "array-uniq": { "version": "1.0.3", "resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.3.tgz", - "integrity": "sha1-r2rId6Jcx/dOBYiUdThY39sk/bY=", + "integrity": "sha512-MNha4BWQ6JbwhFhj03YK552f7cb3AzoE8SzeljgChvL1dl3IcvggXVz1DilzySZkCja+CXuZbdW7yATchWn8/Q==", "optional": true }, "array.prototype.flat": { @@ -27839,7 +27665,7 @@ "bfj": { "version": "4.2.4", "resolved": "https://registry.npmjs.org/bfj/-/bfj-4.2.4.tgz", - "integrity": "sha1-hfeyNoPCr9wVhgOEotHD+sgO0zo=", + "integrity": "sha512-+c08z3TYqv4dy9b0MAchQsxYlzX9D2asHWW4VhO4ZFTnK7v9ps6iNhEQLqJyEZS6x9G0pgOCk/L7B9E4kp8glQ==", "optional": true, "requires": { "check-types": "^7.3.0", @@ -27877,7 +27703,7 @@ "bmp-js": { "version": "0.1.0", "resolved": "https://registry.npmjs.org/bmp-js/-/bmp-js-0.1.0.tgz", - "integrity": "sha1-4Fpj95amwf8l9Hcex62twUjAcjM=", + "integrity": "sha512-vHdS19CnY3hwiNdkaqk93DvjVLfbEcI8mys4UjuWrlX1haDmroo8o4xCzh4wD6DGV6HxRCyauwhHRqMTfERtjw==", "optional": true }, "bn.js": { @@ -28131,13 +27957,13 @@ "buffer-crc32": { "version": "0.2.13", "resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz", - "integrity": "sha1-DTM+PwDqxQqhRUq9MO+MKl2ackI=", + "integrity": "sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==", "optional": true }, "buffer-equal": { "version": "0.0.1", "resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-0.0.1.tgz", - "integrity": "sha1-kbx0sR6kBbyRa8aqkI+q+ltKrEs=", + "integrity": "sha512-RgSV6InVQ9ODPdLWJ5UAqBqJBOg370Nz6ZQtRzpt6nUjc8v0St97uJ4PYC6NztqIScrAXafKM3mZPMygSe1ggA==", "optional": true }, "buffer-from": { @@ -28234,6 +28060,12 @@ "integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==", "dev": true }, + "quick-lru": { + "version": "5.1.1", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", + "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==", + "dev": true + }, "type-fest": { "version": "1.4.0", "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz", @@ -29648,13 +29480,6 @@ "integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=", "dev": true }, - "source-map": { - "version": "0.6.1", - "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz", - "integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==", - "dev": true, - "optional": true - }, "type-check": { "version": "0.3.2", "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz", @@ -30767,9 +30592,9 @@ "devOptional": true }, "fs-extra": { - "version": "10.0.1", - "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.0.1.tgz", - "integrity": "sha512-NbdoVMZso2Lsrn/QwLXOy6rm0ufY2zEOKCDzJR/0kBsb0E6qed0P3iYK+Ath3BfvXEeu4JhEtXLgILx5psUfag==", + "version": "10.1.0", + "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.1.0.tgz", + "integrity": "sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==", "optional": true, "requires": { "graceful-fs": "^4.2.0", @@ -30791,12 +30616,6 @@ "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", "devOptional": true }, - "fsevents": { - "version": "2.3.2", - "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz", - "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==", - "optional": true - }, "function-bind": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz", @@ -30819,39 +30638,6 @@ "https-proxy-agent": "^5.0.0", "is-stream": "^2.0.0", "node-fetch": "^2.6.1" - }, - "dependencies": { - "node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "dev": true, - "requires": { - "whatwg-url": "^5.0.0" - } - }, - "tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "dev": true - }, - "webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "dev": true - }, - "whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "dev": true, - "requires": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - } } }, "gemoji": { @@ -30918,12 +30704,12 @@ "dev": true }, "gifwrap": { - "version": "0.9.2", - "resolved": "https://registry.npmjs.org/gifwrap/-/gifwrap-0.9.2.tgz", - "integrity": "sha512-fcIswrPaiCDAyO8xnWvHSZdWChjKXUanKKpAiWWJ/UTkEi/aYKn5+90e7DE820zbEaVR9CE2y4z9bzhQijZ0BA==", + "version": "0.9.4", + "resolved": "https://registry.npmjs.org/gifwrap/-/gifwrap-0.9.4.tgz", + "integrity": "sha512-MDMwbhASQuVeD4JKd1fKgNgCRL3fGqMM4WaqpNhWO0JiMOAjbQdumbs4BbBZEy9/M00EHEjKN3HieVhCUlwjeQ==", "optional": true, "requires": { - "image-q": "^1.1.1", + "image-q": "^4.0.0", "omggif": "^1.0.10" } }, @@ -31644,6 +31430,13 @@ "requires": { "quick-lru": "^5.1.1", "resolve-alpn": "^1.0.0" + }, + "dependencies": { + "quick-lru": { + "version": "5.1.1", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", + "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==" + } } }, "https-browserify": { @@ -31699,10 +31492,21 @@ "dev": true }, "image-q": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/image-q/-/image-q-1.1.1.tgz", - "integrity": "sha1-/IQJlmRGC5DKhi2TALa/u7+/gFY=", - "optional": true + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/image-q/-/image-q-4.0.0.tgz", + "integrity": "sha512-PfJGVgIfKQJuq3s0tTDOKtztksibuUEbJQIYT3by6wctQo+Rdlh7ef4evJ5NCdxY4CfMbvFkocEwbl4BF8RlJw==", + "optional": true, + "requires": { + "@types/node": "16.9.1" + }, + "dependencies": { + "@types/node": { + "version": "16.9.1", + "resolved": "https://registry.npmjs.org/@types/node/-/node-16.9.1.tgz", + "integrity": "sha512-QpLcX9ZSsq3YYUUnD3nFDY8H7wctAhQj/TFKL8Ya8v5fMm3CFXxo8zStsLAl780ltoYoo1WvKUVGBQK+1ifr7g==", + "optional": true + } + } }, "image-size": { "version": "1.0.0", @@ -34824,14 +34628,6 @@ } } }, - "node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "requires": { - "whatwg-url": "^5.0.0" - } - }, "node-releases": { "version": "1.1.77", "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-1.1.77.tgz", @@ -34878,11 +34674,6 @@ } } }, - "tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=" - }, "watchpack": { "version": "2.1.1", "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.1.1.tgz", @@ -34891,20 +34682,6 @@ "glob-to-regexp": "^0.4.1", "graceful-fs": "^4.1.2" } - }, - "webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=" - }, - "whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "requires": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } } } }, @@ -34930,6 +34707,35 @@ "propagate": "^2.0.0" } }, + "node-fetch": { + "version": "2.6.7", + "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", + "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", + "requires": { + "whatwg-url": "^5.0.0" + }, + "dependencies": { + "tr46": { + "version": "0.0.3", + "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", + "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=" + }, + "webidl-conversions": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", + "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=" + }, + "whatwg-url": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", + "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", + "requires": { + "tr46": "~0.0.3", + "webidl-conversions": "^3.0.0" + } + } + } + }, "node-html-parser": { "version": "1.4.9", "resolved": "https://registry.npmjs.org/node-html-parser/-/node-html-parser-1.4.9.tgz", @@ -35554,15 +35360,15 @@ } }, "glob": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz", - "integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==", + "version": "7.2.3", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz", + "integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==", "optional": true, "requires": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", "inherits": "2", - "minimatch": "^3.0.4", + "minimatch": "^3.1.1", "once": "^1.3.0", "path-is-absolute": "^1.0.0" } @@ -35679,19 +35485,19 @@ "ansi-regex": { "version": "2.1.1", "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.1.1.tgz", - "integrity": "sha1-w7M6te42DYbg5ijwRorn7yfWVN8=", + "integrity": "sha512-TIGnTpdo+E3+pCyAluZvtED5p5wCqLdezCyhPZzKPcxvFplEt4i+W7OONCKgeZFT3+y5NZZfOOS/Bdcanm1MYA==", "optional": true }, "ansi-styles": { "version": "2.2.1", "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.2.1.tgz", - "integrity": "sha1-tDLdM1i2NM914eRmQ2gkBTPB3b4=", + "integrity": "sha512-kmCevFghRiWM7HB5zTPULl4r9bVFSWjz62MhqizDGUrq2NWuNMQyuv4tHHoKJHs69M/MF64lEcHdYIocrdWQYA==", "optional": true }, "array-union": { "version": "1.0.2", "resolved": "https://registry.npmjs.org/array-union/-/array-union-1.0.2.tgz", - "integrity": "sha1-mjRBDk9OPaI96jdb5b5w8kd47Dk=", + "integrity": "sha512-Dxr6QJj/RdU/hCaBjOfxW+q6lyuVE6JFWIrAUpuOOhoJJoQ99cUn3igRaHVB5P9WrgFVN0FfArM3x0cueOU8ng==", "optional": true, "requires": { "array-uniq": "^1.0.1" @@ -35710,7 +35516,7 @@ "chalk": { "version": "1.1.3", "resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.3.tgz", - "integrity": "sha1-qBFcVeSnAv5NFQq9OHKCKn4J/Jg=", + "integrity": "sha512-U3lRVLMSlsCfjqYPbLyVv11M9CPW4I728d6TCKMAOJueEeB9/8o+eSsMnxPJD+Q+K909sdESg7C+tIkoH6on1A==", "optional": true, "requires": { "ansi-styles": "^2.2.1", @@ -35762,15 +35568,15 @@ } }, "glob": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz", - "integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==", + "version": "7.2.3", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz", + "integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==", "optional": true, "requires": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", "inherits": "2", - "minimatch": "^3.0.4", + "minimatch": "^3.1.1", "once": "^1.3.0", "path-is-absolute": "^1.0.0" } @@ -35827,15 +35633,6 @@ "minimist": "^1.2.6" } }, - "node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "optional": true, - "requires": { - "whatwg-url": "^5.0.0" - } - }, "puppeteer": { "version": "1.19.0", "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-1.19.0.tgz", @@ -35876,28 +35673,6 @@ "integrity": "sha1-U10EXOa2Nj+kARcIRimZXp3zJMc=", "optional": true }, - "tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "optional": true - }, - "webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "optional": true - }, - "whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "optional": true, - "requires": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - }, "ws": { "version": "6.2.2", "resolved": "https://registry.npmjs.org/ws/-/ws-6.2.2.tgz", @@ -36240,9 +36015,9 @@ } }, "parse-headers": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/parse-headers/-/parse-headers-2.0.3.tgz", - "integrity": "sha512-QhhZ+DCCit2Coi2vmAKbq5RGTRcQUOE2+REgv8vdyu7MnYx2eZztegqtTx99TZ86GTIwqiy3+4nQTWZ2tgmdCA==", + "version": "2.0.5", + "resolved": "https://registry.npmjs.org/parse-headers/-/parse-headers-2.0.5.tgz", + "integrity": "sha512-ft3iAoLOB/MlwbNXgzy43SWGP6sQki2jQvAyBg/zDFAgr9bfNWZIUj42Kw2eJIl8kEi4PbgE6U1Zau/HwI75HA==", "optional": true }, "parse-json": { @@ -36728,39 +36503,6 @@ "tar-fs": "^2.0.0", "unbzip2-stream": "^1.3.3", "ws": "^7.2.3" - }, - "dependencies": { - "node-fetch": { - "version": "2.6.7", - "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz", - "integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==", - "optional": true, - "requires": { - "whatwg-url": "^5.0.0" - } - }, - "tr46": { - "version": "0.0.3", - "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", - "integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=", - "optional": true - }, - "webidl-conversions": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", - "integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=", - "optional": true - }, - "whatwg-url": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", - "integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=", - "optional": true, - "requires": { - "tr46": "~0.0.3", - "webidl-conversions": "^3.0.0" - } - } } }, "qs": { @@ -36793,9 +36535,9 @@ "dev": true }, "quick-lru": { - "version": "5.1.1", - "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", - "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==" + "version": "6.1.0", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-6.1.0.tgz", + "integrity": "sha512-8HdyR8c0jNVWbYrhUWs9Tg/qAAHgjuJoOIX+mP3eIhgqPO9ytMRURCEFTkOxaHLLsEXo0Cm+bXO5ULuGez+45g==" }, "random-bytes": { "version": "1.0.0", @@ -40026,9 +39768,9 @@ "optional": true }, "got": { - "version": "12.0.3", - "resolved": "https://registry.npmjs.org/got/-/got-12.0.3.tgz", - "integrity": "sha512-hmdcXi/S0gcAtDg4P8j/rM7+j3o1Aq6bXhjxkDhRY2ipe7PHpvx/14DgTY2czHOLaGeU8VRvRecidwfu9qdFug==", + "version": "12.0.4", + "resolved": "https://registry.npmjs.org/got/-/got-12.0.4.tgz", + "integrity": "sha512-2Eyz4iU/ktq7wtMFXxzK7g5p35uNYLLdiZarZ5/Yn3IJlNEpBd5+dCgcAyxN8/8guZLszffwe3wVyw+DEVrpBg==", "optional": true, "requires": { "@sindresorhus/is": "^4.6.0", @@ -40047,9 +39789,9 @@ } }, "http2-wrapper": { - "version": "2.1.10", - "resolved": "https://registry.npmjs.org/http2-wrapper/-/http2-wrapper-2.1.10.tgz", - "integrity": "sha512-QHgsdYkieKp+6JbXP25P+tepqiHYd+FVnDwXpxi/BlUcoIB0nsmTOymTNvETuTO+pDuwcSklPE72VR3DqV+Haw==", + "version": "2.1.11", + "resolved": "https://registry.npmjs.org/http2-wrapper/-/http2-wrapper-2.1.11.tgz", + "integrity": "sha512-aNAk5JzLturWEUiuhAN73Jcbq96R7rTitAoXV54FYMatvihnpD2+6PUgU4ce3D/m5VDbw+F5CsyKSF176ptitQ==", "optional": true, "requires": { "quick-lru": "^5.1.1", @@ -40073,6 +39815,12 @@ "resolved": "https://registry.npmjs.org/p-cancelable/-/p-cancelable-3.0.0.tgz", "integrity": "sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw==", "optional": true + }, + "quick-lru": { + "version": "5.1.1", + "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", + "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==", + "optional": true } } }, diff --git a/package.json b/package.json index 354a8996f8..2920614ef9 100644 --- a/package.json +++ b/package.json @@ -62,6 +62,7 @@ "overload-protection": "^1.2.3", "parse5": "^6.0.1", "port-used": "^2.0.8", + "quick-lru": "6.1.0", "react": "^17.0.2", "react-dom": "^17.0.2", "react-markdown": "^8.0.0", diff --git a/pages/[versionId]/rest/[category]/index.tsx b/pages/[versionId]/rest/[category]/index.tsx index c5476bc0f0..f142e301d7 100644 --- a/pages/[versionId]/rest/[category]/index.tsx +++ b/pages/[versionId]/rest/[category]/index.tsx @@ -40,9 +40,9 @@ export default function Category({ return ( - {/* When the page is the rest product landing page, we don't want to + {/* When the page is the rest product landing page, we don't want to render the rest-specific sidebar because toggling open the categories - won't have the minitoc items at that level. These are pages that have + won't have the minitoc items at that level. These are pages that have category - subcategory - and operations */} {relativePath?.endsWith('index.md') ? ( @@ -133,8 +133,8 @@ export const getServerSideProps: GetServerSideProps = async (context) => const fullPath = `/${context.locale}${versionPathSegment}rest/${context.params?.category}/${subCat}${miniTocAnchor}` restSubcategoryTocs.push({ - fullPath: fullPath, - title: title, + fullPath, + title, }) }) diff --git a/pages/_app.tsx b/pages/_app.tsx index eab4108e82..27494db15f 100644 --- a/pages/_app.tsx +++ b/pages/_app.tsx @@ -10,14 +10,27 @@ import '../stylesheets/index.scss' import events from 'components/lib/events' import experiment from 'components/lib/experiment' import { LanguagesContext, LanguagesContextT } from 'components/context/LanguagesContext' +import { + DotComAuthenticatedContext, + DotComAuthenticatedContextT, +} from 'components/context/DotComAuthenticatedContext' import { defaultComponentTheme } from 'lib/get-theme.js' type MyAppProps = AppProps & { csrfToken: string + isDotComAuthenticated: boolean themeProps: typeof defaultComponentTheme & Pick languagesContext: LanguagesContextT + dotComAuthenticatedContext: DotComAuthenticatedContextT } -const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext }: MyAppProps) => { +const MyApp = ({ + Component, + pageProps, + csrfToken, + themeProps, + languagesContext, + dotComAuthenticatedContext, +}: MyAppProps) => { useEffect(() => { events() experiment() @@ -58,7 +71,9 @@ const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext } preventSSRMismatch > - + + + @@ -66,6 +81,10 @@ const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext } ) } +// Remember, function is only called once if the rendered page can +// be in-memory cached. But still, the `` component will be +// executed every time **in the client** if it was the first time +// ever (since restart) or from a cached HTML. MyApp.getInitialProps = async (appContext: AppContext) => { const { ctx } = appContext // calls page's `getInitialProps` and fills `appProps.pageProps` @@ -78,7 +97,8 @@ MyApp.getInitialProps = async (appContext: AppContext) => { ...appProps, themeProps: getTheme(req), csrfToken: req?.csrfToken?.() || '', - languagesContext: { languages: req.context.languages }, + languagesContext: { languages: req.context.languages, userLanguage: req.context.userLanguage }, + dotComAuthenticatedContext: { isDotComAuthenticated: Boolean(req.cookies?.dotcom_user) }, } } diff --git a/script/graphql/utils/prerender-graphql.js b/script/graphql/utils/prerender-graphql.js index 965468c5b9..f342b85760 100644 --- a/script/graphql/utils/prerender-graphql.js +++ b/script/graphql/utils/prerender-graphql.js @@ -24,7 +24,7 @@ export default async function prerender(context, type, includeFilename) { const html = htmlArray.join('\n') return { - html: html, + html, miniToc: getMiniTocItems(html), } } diff --git a/script/search/sync.js b/script/search/sync.js index 81d995118e..cde5e30147 100644 --- a/script/search/sync.js +++ b/script/search/sync.js @@ -11,6 +11,7 @@ import LunrIndex from './lunr-search-index.js' // Build a search data file for every combination of product version and language // e.g. `github-docs-dotcom-en.json` and `github-docs-2.14-ja.json` export default async function syncSearchIndexes(opts = {}) { + const t0 = new Date() if (opts.language) { if (!Object.keys(languages).includes(opts.language)) { console.log( @@ -89,6 +90,9 @@ export default async function syncSearchIndexes(opts = {}) { } } } + const t1 = new Date() + const tookSec = (t1.getTime() - t0.getTime()) / 1000 console.log('\nDone!') + console.log(`Took ${tookSec.toFixed(1)} seconds`) } diff --git a/tests/helpers/script-data.js b/tests/helpers/script-data.js new file mode 100644 index 0000000000..fd4887edb8 --- /dev/null +++ b/tests/helpers/script-data.js @@ -0,0 +1,29 @@ +const NEXT_DATA_QUERY = 'script#__NEXT_DATA__' +const PRIMER_DATA_QUERY = 'script#__PRIMER_DATA__' + +function getScriptData($, key) { + const data = $(key) + if (!data.length === 1) { + throw new Error(`Not exactly 1 element match for '${key}'. Found ${data.length}`) + } + return JSON.parse(data.get()[0].children[0].data) +} + +export const getNextData = ($) => getScriptData($, NEXT_DATA_QUERY) +export const getPrimerData = ($) => getScriptData($, PRIMER_DATA_QUERY) + +export const getUserLanguage = ($) => { + // Because the page might come from the middleware rendering cache, + // the DOM won't get updated until the first client-side React render. + // But we can assert the data that would be used for that first render. + const { props } = getNextData($) + return props.languagesContext.userLanguage +} + +export const getIsDotComAuthenticated = ($) => { + // Because the page might come from the middleware rendering cache, + // the DOM won't get updated until the first client-side React render. + // But we can assert the data that would be used for that first render. + const { props } = getNextData($) + return props.dotComAuthenticatedContext.isDotComAuthenticated +} diff --git a/tests/meta/repository-references.js b/tests/meta/repository-references.js index b70eeede18..6abcc6c54a 100644 --- a/tests/meta/repository-references.js +++ b/tests/meta/repository-references.js @@ -25,6 +25,8 @@ const PUBLIC_REPOS = new Set([ 'codeql-action-sync-tool', 'codeql-action', 'codeql-cli-binaries', + 'codeql', + 'codeql-go', 'platform-samples', 'github-services', 'explore', diff --git a/tests/rendering/head.js b/tests/rendering/head.js index 1a117d8c60..111ca523ca 100644 --- a/tests/rendering/head.js +++ b/tests/rendering/head.js @@ -13,7 +13,16 @@ describe('', () => { expect($hreflangs.length).toEqual(Object.keys(languages).length) expect($('link[href="https://docs.github.com/cn"]').length).toBe(1) expect($('link[href="https://docs.github.com/ja"]').length).toBe(1) - expect($('link[hrefLang="en"]').length).toBe(1) + // Due to a bug in either NextJS, JSX, or TypeScript, + // when put `` in a .tsx file, this incorrectly + // gets rendered out as `` in the final HTML. + // Note the uppercase L. It's supposed to become ``. + // When cheerio serializes to HTML, it gets this right so it lowercases + // the attribute. So if this rendering in this jest test was the first + // ever cold hit, you might get the buggy HTML from React or you + // might get the correct HTML from cheerio's `.html()` serializer. + // This is why we're looking for either. + expect($('link[hreflang="en"]').length + $('link[hrefLang="en"]').length).toBe(1) }) test('includes page intro in `description` meta tag', async () => { diff --git a/tests/rendering/header.js b/tests/rendering/header.js index 78c223a31d..221c15ac21 100644 --- a/tests/rendering/header.js +++ b/tests/rendering/header.js @@ -1,7 +1,8 @@ -import { jest } from '@jest/globals' +import { expect, jest } from '@jest/globals' import { getDOM } from '../helpers/e2etest.js' import { oldestSupported } from '../../lib/enterprise-server-releases.js' +import { getUserLanguage } from '../helpers/script-data.js' describe('header', () => { jest.setTimeout(5 * 60 * 1000) @@ -91,54 +92,31 @@ describe('header', () => { test("renders a link to the same page in user's preferred language, if available", async () => { const headers = { 'accept-language': 'ja' } const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) - expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) + expect(getUserLanguage($)).toBe('ja') }) test("renders a link to the same page if user's preferred language is Chinese - PRC", async () => { const headers = { 'accept-language': 'zh-CN' } const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) - expect($('[data-testid=header-notification] a[href*="/cn"]').length).toBe(1) - }) - - test("does not render a link when user's preferred language is Chinese - Taiwan", async () => { - const headers = { 'accept-language': 'zh-TW' } - const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification]').length).toBe(0) - }) - - test("does not render a link when user's preferred language is English", async () => { - const headers = { 'accept-language': 'en' } - const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification]').length).toBe(0) + expect(getUserLanguage($)).toBe('cn') }) test("renders a link to the same page in user's preferred language from multiple, if available", async () => { const headers = { 'accept-language': 'ja, *;q=0.9' } const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) - expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) + expect(getUserLanguage($)).toBe('ja') }) test("renders a link to the same page in user's preferred language with weights, if available", async () => { const headers = { 'accept-language': 'ja;q=1.0, *;q=0.9' } const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) - expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) + expect(getUserLanguage($)).toBe('ja') }) test("renders a link to the user's 2nd preferred language if 1st is not available", async () => { const headers = { 'accept-language': 'zh-TW,zh;q=0.9,ja *;q=0.8' } const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) - expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) - }) - - test('renders no notices if no language preference is available', async () => { - const headers = { 'accept-language': 'zh-TW,zh;q=0.9,zh-SG *;q=0.8' } - const $ = await getDOM('/en', { headers }) - expect($('[data-testid=header-notification]').length).toBe(0) + expect(getUserLanguage($)).toBe('ja') }) }) diff --git a/tests/rendering/render-caching.js b/tests/rendering/render-caching.js new file mode 100644 index 0000000000..49c0a2442d --- /dev/null +++ b/tests/rendering/render-caching.js @@ -0,0 +1,160 @@ +import cheerio from 'cheerio' +import { expect, jest, test } from '@jest/globals' + +import { get } from '../helpers/e2etest.js' +import { PREFERRED_LOCALE_COOKIE_NAME } from '../../middleware/detect-language.js' +import { + getNextData, + getPrimerData, + getUserLanguage, + getIsDotComAuthenticated, +} from '../helpers/script-data.js' + +const serializeTheme = (theme) => { + return encodeURIComponent(JSON.stringify(theme)) +} + +describe('in-memory render caching', () => { + jest.setTimeout(30 * 1000) + + test('second render should be a cache hit with different csrf-token', async () => { + const res = await get('/en') + // Because these are effectively end-to-end tests, you can't expect + // the first request to be a cache miss because another end-to-end + // test might have "warmed up" this endpoint. + expect(res.headers['x-middleware-cache']).toBeTruthy() + const $1 = cheerio.load(res.text) + const res2 = await get('/en') + expect(res2.headers['x-middleware-cache']).toBe('hit') + const $2 = cheerio.load(res2.text) + const csrfTokenHTML1 = $1('meta[name="csrf-token"]').attr('content') + const csrfTokenHTML2 = $2('meta[name="csrf-token"]').attr('content') + expect(csrfTokenHTML1).not.toBe(csrfTokenHTML2) + // The HTML is one thing, we also need to check that the + // __NEXT_DATA__ serialized (JSON) state is different. + const csrfTokenNEXT1 = getNextData($1).props.csrfToken + const csrfTokenNEXT2 = getNextData($2).props.csrfToken + expect(csrfTokenHTML1).toBe(csrfTokenNEXT1) + expect(csrfTokenHTML2).toBe(csrfTokenNEXT2) + expect(csrfTokenNEXT1).not.toBe(csrfTokenNEXT2) + }) + + test('second render should be a cache hit with different dotcom-auth', async () => { + // Anonymous first + const res = await get('/en') + // Because these are effectively end-to-end tests, you can't expect + // the first request to be a cache miss because another end-to-end + // test might have "warmed up" this endpoint. + expect(res.headers['x-middleware-cache']).toBeTruthy() + const $1 = cheerio.load(res.text) + const res2 = await get('/en', { + headers: { + cookie: 'dotcom_user=peterbe', + }, + }) + expect(res2.headers['x-middleware-cache']).toBe('hit') + const $2 = cheerio.load(res2.text) + // The HTML is one thing, we also need to check that the + // __NEXT_DATA__ serialized (JSON) state is different. + const dotcomAuthNEXT1 = getIsDotComAuthenticated($1) + const dotcomAuthNEXT2 = getIsDotComAuthenticated($2) + expect(dotcomAuthNEXT1).not.toBe(dotcomAuthNEXT2) + }) + + test('second render should be a cache hit with different theme properties', async () => { + const cookieValue1 = { + color_mode: 'light', + light_theme: { name: 'light', color_mode: 'light' }, + dark_theme: { name: 'dark_high_contrast', color_mode: 'dark' }, + } + // Light mode first + const res1 = await get('/en', { + headers: { + cookie: `color_mode=${serializeTheme(cookieValue1)}`, + }, + }) + // Because these are effectively end-to-end tests, you can't expect + // the first request to be a cache miss because another end-to-end + // test might have "warmed up" this endpoint. + expect(res1.headers['x-middleware-cache']).toBeTruthy() + const $1 = cheerio.load(res1.text) + expect($1('body').data('color-mode')).toBe(cookieValue1.color_mode) + const themeProps1 = getNextData($1).props.themeProps + expect(themeProps1.colorMode).toBe('day') + + const cookieValue2 = { + color_mode: 'dark', + light_theme: { name: 'light', color_mode: 'light' }, + dark_theme: { name: 'dark_high_contrast', color_mode: 'dark' }, + } + const res2 = await get('/en', { + headers: { + cookie: `color_mode=${serializeTheme(cookieValue2)}`, + }, + }) + expect(res2.headers['x-middleware-cache']).toBeTruthy() + const $2 = cheerio.load(res2.text) + expect($2('body').data('color-mode')).toBe(cookieValue2.color_mode) + const themeProps2 = getNextData($2).props.themeProps + expect(themeProps2.colorMode).toBe('night') + }) + + test('second render should be cache hit with different resolvedServerColorMode in __PRIMER_DATA__', async () => { + await get('/en') // first render to assert the next render comes from cache + + const res = await get('/en', { + headers: { + cookie: `color_mode=${serializeTheme({ + color_mode: 'dark', + light_theme: { name: 'light', color_mode: 'light' }, + dark_theme: { name: 'dark_high_contrast', color_mode: 'dark' }, + })}`, + }, + }) + expect(res.headers['x-middleware-cache']).toBeTruthy() + const $ = cheerio.load(res.text) + const data = getPrimerData($) + expect(data.resolvedServerColorMode).toBe('night') + + // Now do it all over again but with a light color mode + const res2 = await get('/en', { + headers: { + cookie: `color_mode=${serializeTheme({ + color_mode: 'light', + light_theme: { name: 'light', color_mode: 'light' }, + dark_theme: { name: 'dark_high_contrast', color_mode: 'dark' }, + })}`, + }, + }) + expect(res2.headers['x-middleware-cache']).toBeTruthy() + const $2 = cheerio.load(res2.text) + const data2 = getPrimerData($2) + expect(data2.resolvedServerColorMode).toBe('day') + }) + + test('user-language, by header, in meta tag', async () => { + await get('/en') // first render to assert the next render comes from cache + + const res = await get('/en', { + headers: { 'accept-language': 'ja;q=1.0, *;q=0.9' }, + }) + expect(res.headers['x-middleware-cache']).toBeTruthy() + const $ = cheerio.load(res.text) + const userLanguage = getUserLanguage($) + expect(userLanguage).toBe('ja') + }) + + test('user-language, by cookie, in meta tag', async () => { + await get('/en') // first render to assert the next render comes from cache + + const res = await get('/en', { + headers: { + Cookie: `${PREFERRED_LOCALE_COOKIE_NAME}=ja`, + }, + }) + expect(res.headers['x-middleware-cache']).toBeTruthy() + const $ = cheerio.load(res.text) + const userLanguage = getUserLanguage($) + expect(userLanguage).toBe('ja') + }) +}) diff --git a/tests/rendering/signup-button.js b/tests/rendering/signup-button.js index 64881cdab8..673f9521b5 100644 --- a/tests/rendering/signup-button.js +++ b/tests/rendering/signup-button.js @@ -1,23 +1,14 @@ import { jest, describe, expect } from '@jest/globals' import { getDOM } from '../helpers/e2etest.js' +import { getIsDotComAuthenticated } from '../helpers/script-data.js' describe('GHEC sign up button', () => { jest.setTimeout(60 * 1000) - test('present by default', async () => { + test('false by default', async () => { const $ = await getDOM('/en') - expect($('a[href^="https://github.com/signup"]').length).toBeGreaterThan(0) - }) - - test('present on enterprise-cloud pages', async () => { - const $ = await getDOM('/en/enterprise-cloud@latest') - expect($('a[href^="https://github.com/signup"]').length).toBeGreaterThan(0) - }) - - test('not present on enterprise-server pages', async () => { - const $ = await getDOM('/en/enterprise-server@latest') - expect($('a[href^="https://github.com/signup"]').length).toBe(0) + expect(getIsDotComAuthenticated($)).toBe(false) }) test('not present if dotcom_user cookie', async () => { @@ -26,6 +17,15 @@ describe('GHEC sign up button', () => { cookie: 'dotcom_user=peterbe', }, }) - expect($('a[href^="https://github.com/signup"]').length).toBe(0) + expect(getIsDotComAuthenticated($)).toBe(true) + + // Do another request, same URL, but different cookie, just to + // make sure the server-side rendering cache isn't failing. + const $2 = await getDOM('/en', { + headers: { + cookie: 'bla=bla', + }, + }) + expect(getIsDotComAuthenticated($2)).toBe(false) }) }) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md index 3904419a2b..a534d62350 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories shortTitle: Administrar el nombre de la rama predeterminada --- diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 9248172dd6..1c5a5ce815 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -103,7 +103,7 @@ steps: ## Almacenar dependencias en caché -Puedes almacenar en caché tus dependencias para acelerar tus ejecuciones de flujo de trabajo. After a successful run, your local Maven repository will be stored in a cache. En las ejecuciones de flujo de trabajo futuras, el caché se restaurará para que las dependencias no necesiten descargarse desde los repositorios remotos de Maven. Puedes guardar las dependencias en caché utilizando simplemente la [acción `setup-java`](https://github.com/marketplace/actions/setup-java-jdk) o puedes utilizar la [Acción `cache`](https://github.com/actions/cache) para tener una configuración personalizada y más avanzada. +Puedes almacenar en caché tus dependencias para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu repositorio local de Maven se almacenará en un caché. En las ejecuciones de flujo de trabajo futuras, el caché se restaurará para que las dependencias no necesiten descargarse desde los repositorios remotos de Maven. Puedes guardar las dependencias en caché utilizando simplemente la [acción `setup-java`](https://github.com/marketplace/actions/setup-java-jdk) o puedes utilizar la [Acción `cache`](https://github.com/actions/cache) para tener una configuración personalizada y más avanzada. ```yaml{:copy} steps: diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 056b773707..7d5fd22022 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -65,7 +65,7 @@ Los siguientes ejemplos demuestran el uso de la acción `fwal/setup-swift`. ### Utilizar versiones múltiples de Swift -You can configure your job to use multiple versions of Swift in a matrix. +Puedes configurar tu job para que utilice versiones múltiples de Swift en una matriz. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md index 5ef8b89547..398293ed92 100644 --- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md @@ -50,7 +50,7 @@ Para ayudar a prevenir la divulgación accidental, {% data variables.product.pro {% warning %} -**Warning**: Any user with write access to your repository has read access to all secrets configured in your repository. Therefore, you should ensure that the credentials being used within workflows have the least privileges required. +**Advertencia**: Cualquier usuario con acceso de escritura a tu repositorio tiene acceso de lectura para todos los secretos que se configuraron en tu repositorio. Por lo tanto, debes asegurarte de que las credenciales que están utilizando con los flujos de trabajo tienen los mínimos privilegios requeridos. {% endwarning %} @@ -202,9 +202,9 @@ El mismo principio que se describió anteriormente para utilizar acciones de ter {% endif %} {% if allow-actions-to-approve-pr %} -## Preventing {% data variables.product.prodname_actions %} from {% if allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests +## Prevenir que {% data variables.product.prodname_actions %} {% if allow-actions-to-approve-pr-with-ent-repo %}cree o {% endif %}apruebe solicitudes de cambios -{% data reusables.actions.workflow-pr-approval-permissions-intro %} Allowing workflows, or any other automation, to {% if allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests could be a security risk if the pull request is merged without proper oversight. +{% data reusables.actions.workflow-pr-approval-permissions-intro %} El permitir que los flujos de trabajo o cualquier otra automatzización {% if allow-actions-to-approve-pr-with-ent-repo %}creen o {% endif %}aprueben solicitudes de cambio podría representar un riesgo de seguridad si la solicitud de cambios se fusiona sin una supervisión adecuada. Para obtener más información sobre cómo configurar este ajuste, consulta la secciones {% if allow-actions-to-approve-pr-with-ent-repo %}{% ifversion ghes or ghec or ghae %}"[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)",{% endif %}{% endif %} "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-{% if allow-actions-to-approve-pr-with-ent-repo %}creating-or-{% endif %}approving-pull-requests)"{% if allow-actions-to-approve-pr-with-ent-repo %} y "[Administrar los ajustes de las {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"{% endif %}. {% endif %} @@ -264,9 +264,9 @@ Esta lista describe los acercamientos recomendatos para acceder alos datos de un 3. **Tokens de {% data variables.product.prodname_github_app %}** - Las {% data variables.product.prodname_github_apps %} pueden instalarse en los repositorios seleccionados, e incluso tienen permisos granulares en los recursos dentro de ellos. Puedes crear una {% data variables.product.prodname_github_app %} interna a tu organización, instalarla en los repositorios a los que necesites tener acceso dentro de tu flujo de trabajo, y autenticarte como la instalación dentro del flujo de trabajo para acceder a esos repositorios. 4. **Tokens de acceso personal** - - Jamás debes utilizar tokens de acceso personal desde tu propia cuenta. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Adicionalmente, si sales de una organización más adelante, los flujos de trabajo que utilicen este token fallarán inmediatamente, y depurar este problema puede ser difícil. + - Jamás debes utilizar tokens de acceso personal desde tu propia cuenta. Estos token otorgan acceso a todos los repositorios dentro de las organizaciones a las cuales tienes acceso, así como a todos los repositorios personales de tu cuenta personal. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Adicionalmente, si sales de una organización más adelante, los flujos de trabajo que utilicen este token fallarán inmediatamente, y depurar este problema puede ser difícil. - Si se utiliza un token de acceso personal, debe ser uno que se haya generado para una cuenta nueva a la que solo se le haya otorgado acceso para los repositorios específicos que se requieren para el flujo de trabajo. Nota que este acercamiento no es escalable y debe evitarse para favorecer otras alternativas, tales como las llaves de despliegue. -5. **SSH keys on a personal account** +5. **Llaves SSH en una cuenta personal** - Los flujos de trabajo jamás deben utilizar las llaves SSH en una cuenta personal. De forma similar a los tokens de acceso personal, estas otorgan permisos de lectura/escritura a todos tus repositorios personales así como a todos los repositorios a los que tengas acceso mediante la membercía de organización. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Si pretendes utilizar una llave SSH porque solo necesitas llevar a cabo clonados de repositorio o subidas a éste, y no necesitas interactuar con una API pública, entonces mejor deberías utilizar llaves de despliegue individuales. ## Fortalecimiento para los ejecutores auto-hospedados diff --git a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md index 47b02d52e7..54950a2f8a 100644 --- a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md @@ -23,7 +23,7 @@ topics: Los contenedores de servicios son contenedores de Docker que ofrecen una manera sencilla y portátil de alojar servicios que probablemente necesites para probar o usar tu aplicación en un flujo de trabajo. Por ejemplo, es posible que tu flujo de trabajo tenga que ejecutar pruebas de integración que requieran acceso a una base de datos y a una memoria caché. -Puedes configurar contenedores de servicios para cada trabajo en un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea un contenedor de Docker nuevo para cada servicio configurado en el flujo de trabajo y destruye el contenedor de servicios cuando se termina el trabajo. Los pasos de un trabajo pueden comunicarse con todos los contenedores de servicios que son parte del mismo trabajo. However, you cannot create and use service containers inside a composite action. +Puedes configurar contenedores de servicios para cada trabajo en un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea un contenedor de Docker nuevo para cada servicio configurado en el flujo de trabajo y destruye el contenedor de servicios cuando se termina el trabajo. Los pasos de un trabajo pueden comunicarse con todos los contenedores de servicios que son parte del mismo trabajo. Sin embargo, no puedes crear y utilizar contenedores de servicio dentro de una acción compuesta. {% data reusables.actions.docker-container-os-support %} @@ -49,7 +49,7 @@ Cuando un trabajo se ejecuta directamente en una máquina del ejecutor, el servi Puedes usar la palabra clave `services` para crear contenedores de servicios que sean parte de un trabajo en tu flujo de trabajo. Para obtener más información, consulta [`jobs..services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices). -Este ejemplo crea un servicio llamado `redis` en un trabajo llamado `container-job`. The Docker host in this example is the `node:16-bullseye` container. +Este ejemplo crea un servicio llamado `redis` en un trabajo llamado `container-job`. El host de Docker en este ejemplo es el contenedor `node:16-bullseye`. {% raw %} ```yaml{:copy} diff --git a/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md index 9912a736e3..7a48cd7eb3 100644 --- a/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md +++ b/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md @@ -70,7 +70,7 @@ Puedes crear un flujo de trabajo de integración continua (CI) para construir y El resultado de la construcción y la prueba de tu código frecuentemente produce archivos que puedes usar para depurar fallas de prueba y códigos de producción que puedes implementar. Puedes configurar un flujo de trabajo para construir y probar el código subido a tu repositorio e informar un estado satisfactorio o de falla. Puedes cargar los resultados de construcción y prueba para usar en implementaciones, pruebas de depuración fallidas o fallos, y para visualizar la cobertura del conjunto de prueba. -Puedes usar la acción `upload-Artifact` para cargar artefactos. Cuando cargues un artefacto, puedes especificar un archivo sencillo o un directorio, o varios archivos o directorios. También puedes excluir ciertos archivos o directorios y utilizar patrones de comodín. Te recomendamos que proporciones un nombre para cada artefacto pero, si no se lo das, entonces el nombre predeterminado que se utilizará será `artifact`. For more information on syntax, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) action{% else %} `actions/upload-artifact` action on {% data variables.product.product_location %}{% endif %}. +Puedes usar la acción `upload-Artifact` para cargar artefactos. Cuando cargues un artefacto, puedes especificar un archivo sencillo o un directorio, o varios archivos o directorios. También puedes excluir ciertos archivos o directorios y utilizar patrones de comodín. Te recomendamos que proporciones un nombre para cada artefacto pero, si no se lo das, entonces el nombre predeterminado que se utilizará será `artifact`. Para obtener más información sobre la sintaxis, consulta la acción {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact){% else %} `actions/upload-artifact` en {% data variables.product.product_location %}{% endif %}. ### Ejemplo @@ -88,7 +88,7 @@ Por ejemplo, tu repositorio o una aplicación web podrían contener archivos de | ``` -This example shows you how to create a workflow for a Node.js project that builds the code in the `src` directory and runs the tests in the `tests` directory. Puedes suponer que la ejecución `npm test` produce un informe de cobertura de código denominado `code-coverage.html` almacenada en el directorio `output/test/`. +En este ejemplo se muestra cómo crear un flujo de trabajo para un proyecto de Node.js que compila el código en el directorio `src` y ejecuta las pruebas en el directorio `tests`. Puedes suponer que la ejecución `npm test` produce un informe de cobertura de código denominado `code-coverage.html` almacenada en el directorio `output/test/`. El flujo de trabajo carga los artefactos de producción en el directorio `dist`, pero excluye cualquier archivo de markdown. También carga el reporte de `code-coverage.html` como otro artefacto. @@ -141,7 +141,7 @@ El valor `retention-days` no puede exceder el límite de retención que configur Durante una ejecución de flujo de trabajo, puedes utilizar la acción [`download-artifact`](https://github.com/actions/download-artifact) para descargar artefactos que se hayan cargado previamente en la misma ejecución de flujo de trabajo. -Después de que se haya completado una ejecución de flujo de trabajo, puedes descargar o borrar los artefactos en {% data variables.product.prodname_dotcom %} o utilizando la API de REST. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." +Después de que se haya completado una ejecución de flujo de trabajo, puedes descargar o borrar los artefactos en {% data variables.product.prodname_dotcom %} o utilizando la API de REST. Para obtener más información, consulta las secciones "[Descargar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)", "[eliminar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/removing-workflow-artifacts)", y la "[API de REST de Artefactos](/rest/reference/actions#artifacts)". ### Descargar artefactos durante una ejecución de flujo de trabajo @@ -171,7 +171,7 @@ También puedes descargar todos los artefactos en una ejecución de flujo de tra Si descargas todos los artefactos de una ejecución de flujo de trabajo, se creará un directorio para cada uno de ellos utilizando su nombre. -For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.product.product_location %}{% endif %}. +Para obtener más información sobre la sintaxis, consulta la acción {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact){% else %} `actions/download-artifact` en {% data variables.product.product_location %}{% endif %}. ## Pasar datos entre puestos en un flujo de trabajo diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 6cb812451d..d797af7a4f 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Enabling Dependabot for your enterprise -intro: 'You can allow users of {% data variables.product.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' +title: Habilitar al Dependabot en tu empresa +intro: 'Puedes permitir que los usuarios de {% data variables.product.product_location %} encuentren y corrijan las vulnerabilidades de las dependencias de código si habilitas las {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} y las {% data variables.product.prodname_dependabot_updates %}{% endif %}.' miniTocMaxHeadingLevel: 3 shortTitle: Dependabot redirect_from: @@ -24,7 +24,7 @@ topics: - Dependabot --- -## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %} +## Acerca del {% data variables.product.prodname_dependabot %} para {% data variables.product.product_name %} El {% data variables.product.prodname_dependabot %} ayuda a que los usuarios de {% data variables.product.product_location %} encuentren y corrijan vulnerabilidades en sus dependencias.{% ifversion ghes > 3.2 %} Puedes habilitar las {% data variables.product.prodname_dependabot_alerts %} para notificar a los usuarios sobre dependencias vulnerables y {% data variables.product.prodname_dependabot_updates %} para corregir las vulnerabilidades y mantener actualziadas las dependencias a su última versión. @@ -37,19 +37,19 @@ Con las {% data variables.product.prodname_dependabot_alerts %}, {% data variabl {% data reusables.repositories.tracks-vulnerabilities %} -After you enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. Únicamente se sincronizan las asesorías que revisa {% data variables.product.company_short %}. {% data reusables.security-advisory.link-browsing-advisory-db %} +Después de que habilitas las {% data variables.product.prodname_dependabot_alerts %} para tu empresa, los datos de las vulnerabilidades se sincronizan desde la {% data variables.product.prodname_advisory_database %} con tu instancia una vez por hora. Únicamente se sincronizan las asesorías que revisa {% data variables.product.company_short %}. {% data reusables.security-advisory.link-browsing-advisory-db %} También puedes elegir sincronizar manualmente los datos de vulnerabilidad en cualquier momento. Para obtener más información, consulta la sección "[Ver los datos de vulnerabilidad de tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)". {% note %} -**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. +**Nota:** cuando habilitas las {% data variables.product.prodname_dependabot_alerts %}, no se carga código ni información sobre este desde {% data variables.product.product_location %} hacia {% data variables.product.prodname_dotcom_the_website %}. {% endnote %} -When {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in {% data variables.product.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. Puedes elegir si quieres notificar a los usuarios automáticamente acerca de las {% data variables.product.prodname_dependabot_alerts %} nuevas o no. +Cuando {% data variables.product.product_location %} recibe la información sobre una vulnerabilidad, identifica los repositorios de {% data variables.product.product_location %} que utilizan la versión afectada de la dependencia y genera {% data variables.product.prodname_dependabot_alerts %}. Puedes elegir si quieres notificar a los usuarios automáticamente acerca de las {% data variables.product.prodname_dependabot_alerts %} nuevas o no. -Para los repositorios que cuenten con las {% data variables.product.prodname_dependabot_alerts %} habilitadas, el escaneo se activa en cualquier subida a la rama predeterminada. Additionally, when a new vulnerability record is added to {% data variables.product.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.product.product_location %} and generates alerts for any repository that is vulnerable. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". +Para los repositorios que cuenten con las {% data variables.product.prodname_dependabot_alerts %} habilitadas, el escaneo se activa en cualquier subida a la rama predeterminada. Adicionalmente, cuando se agrega un registro de vulnerabilidad nuevo a {% data variables.product.product_location %}, {% data variables.product.product_name %} escanea todos los repositorios existentes en {% data variables.product.product_location %} y genera alertas para cualquier repositorio que esté vulnerable. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". {% ifversion ghes > 3.2 %} ### Acerca de {% data variables.product.prodname_dependabot_updates %} diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 8a3114ec5c..60411c5149 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -39,7 +39,7 @@ Puedes crear tus propias automatizaciones únicas o puedes utilizar y adaptar fl {% ifversion ghec %}Puedes disfrutar la convivencia de los ejecutores hospedados en {% data variables.product.company_short %}, los cuales mantiene y mejora {% data variables.product.company_short %}, o puedes{% else %}Puedes{% endif %} controlar tu propia infraestructura de IC/DC utilizando ejecutores auto-hospedados. Los ejecutores auto-hospedados te permiten determinar el ambiente y recursos exactos que completan tus compilaciones, pruebas y despliegues sin exponer tu ciclo de desarrollo de software a la internet. Para obtener más información, consulta las secciones {% ifversion ghec %}"[Acerca de los ejecutores hospedados por {% data variables.product.company_short %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" y{% endif %} "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)". -Las {% data variables.product.prodname_actions %} proprocionan un control mayor sobre los despliegues. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 or ghes > 3.4 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC proporciona beneficios de seguridad tales como el eliminar la necesidad de almacenar credenciales como secretos de larga duración. Para obtener más información, consulta la sección "[Acerca del fortalecimiento de seguridad con OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".{% endif %} +Las {% data variables.product.prodname_actions %} proprocionan un control mayor sobre los despliegues. Por ejemplo, puedes utilizar ambientes para requerir aprobaciones para que un job pueda proceder, restringir qué ramas pueden activar un flujo de trabajo o limitar el acceso a los secretos.{% ifversion ghec or ghae-issue-4856 or ghes > 3.4 %} Si tus flujos de trabajo necesitan acceder a los recursos desde un proveedor de servicios en la nube que sea compatible con OpenID Conect (OIDC), puedes configurar tus flujos de trabajo para que se autentiquen directamente con dicho proveedor. OIDC proporciona beneficios de seguridad tales como el eliminar la necesidad de almacenar credenciales como secretos de larga duración. Para obtener más información, consulta la sección "[Acerca del fortalecimiento de seguridad con OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".{% endif %} Las {% data variables.product.prodname_actions %} también incluyen herramientas para regir el ciclo de desarrollo de software de tu empresa y satisfacer las obligaciones de cumplimiento. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". diff --git a/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md index 6e96b93281..c4f234984b 100644 --- a/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md +++ b/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Acceder a los reportes de cumplimiento de tu empresa -intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.' +intro: 'Puedes acceder a los reportes de cumplimiento de {% data variables.product.company_short %}, tales como nuestros reportes de SOC y la auto-valoración de CAIQ de la Alianza de Seguridad en la Nube (CSA CAIQ) para tu empresa.' versions: ghec: '*' type: how_to @@ -14,7 +14,7 @@ shortTitle: Acceso a los reportes de cumplimiento ## Acerca de los reportes de cumplimiento de {% data variables.product.company_short %} -You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings. +Puedes acceder a los reportes de cumplimiento de {% data variables.product.company_short %} en los ajustes de tu empresa. {% data reusables.security.compliance-report-list %} @@ -22,7 +22,7 @@ You can access {% data variables.product.company_short %}'s compliance reports i {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %} -1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**. +1. Debajo de "Recursos", a la derecha del reporte al cuál quieres acceder, haz clic en {% octicon "download" aria-label="The Download icon" %} **Descargar** o en {% octicon "link-external" aria-label="The external link icon" %} **Ver**. {% data reusables.security.compliance-report-screenshot %} diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 751f502bac..f503abb34f 100644 --- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -15,7 +15,7 @@ topics: - Secret scanning --- -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change. @@ -33,7 +33,7 @@ You can define custom patterns for your enterprise, organization, or repository. {%- else %} 20 custom patterns for each organization or enterprise account, and per repository. {%- endif %} -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}: diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md index 364fadec90..ce8bce92b1 100644 --- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md @@ -12,7 +12,7 @@ shortTitle: Ver las perspectivas de los debates ## Acerca del tablero de perspectivas de los debates -You can use discussions insights to help understand the contribution activity, page views, and growth of your discussions community. +Puedes utilizar las perspectivas de los debates para que te ayuden a entender la actividad de contribución, vistas de página y crecimiento de tu comunidad de debates. - La **actividad de contribución** muestra la cuenta total de contribuciones para los debates, propuestas y solicitudes de cambio. - Las **vistas de la página de debates** muestra las vistas de página totales para los debates, segmentadas por los usuarios que iniciaron sesión contra los anónimos. - Los **contribuyentes diarios de los debates** muestra el conteo diario de usuarios únicos que reaccionaron, votaron, marcaron una respeusta, comentaron o publicaron en el tiempo seleccionado. @@ -28,7 +28,7 @@ You can use discussions insights to help understand the contribution activity, p ## Ver las perspectivas de los debates -{% data reusables.repositories.navigate-to-repo %} For organization discussions, navigate to the main page of the source repository. +{% data reusables.repositories.navigate-to-repo %} Para los debates organizacionales, navega a la página principal del repositorio fuente. {% data reusables.repositories.accessing-repository-graphs %} 3. En la barra lateral izquierda, haz clic en **Community** (Comunidad). ![Captura de pantalla de la pestaña "Comunidad" en l barra lateral izquierda](/assets/images/help/graphs/graphs-sidebar-community-tab.png) 1. Opcionalmente, en la esquina superior derecha de la página, selecciona el menú desplegable de **Periodo** y haz clic en el periodo de tiempo del cual quieres ver los datos: **30 días**, **3 meses** o **1 año**. ![Captura de pantalla del selector de fechas para las perspectivas de los debates](/assets/images/help/discussions/discussions-dashboard-date-selctor.png) diff --git a/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index ad4b904a22..2d766d181c 100644 --- a/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -17,9 +17,9 @@ shortTitle: Administrar el uso de datos para un repositorio privado ## Acerca del uso de datos para tu repositorio privado -You can control data use for your private repository with the security and analysis features. +Puedes controlar el uso de datos de tu repositorio privado con las características de seguridad y análisis. -- Enable the dependency graph to allow read-only data analysis on your repository. +- Habilita la gráfica de dependencias para permitir un análisis de datos de solo lectura en tu repositorio. - Inhabilita la gráfica de dependencias para bloquear el análisis de datos de solo lectura de tu repositorio. Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a la gráfica de dependencias, en donde puedes rastrear las dependencias de tus repositorios y recibir las {% data variables.product.prodname_dependabot_alerts %} cuando {% data variables.product.product_name %} detecte las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 7e14e81eae..609fce18c6 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -38,7 +38,7 @@ To get the most out of your trial, follow these steps: 1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations). 2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see: - - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast + - [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)" diff --git a/translations/es-ES/content/get-started/using-github/github-mobile.md b/translations/es-ES/content/get-started/using-github/github-mobile.md index 96b5294e26..b17d4051a4 100644 --- a/translations/es-ES/content/get-started/using-github/github-mobile.md +++ b/translations/es-ES/content/get-started/using-github/github-mobile.md @@ -26,11 +26,11 @@ Con {% data variables.product.prodname_mobile %} puedes: - Buscar, navegar e interactuar con usuarios, repositorios y organizaciones - Recibir notificaciones para subir información cuando alguien menciona tu nombre de usuario {% ifversion fpt or ghec %}- Asegura tu cuenta de GitHub.com con la autenticación bifactorial -- Verify your sign in attempts on unrecognized devices{% endif %} +- Verificar tus intentos de inicio de sesión en dispositivos no reconocidos{% endif %} Para obtener más información sobre las notificaciones de {% data variables.product.prodname_mobile %}, consulta "[Configurando notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." -{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} +{% ifversion fpt or ghec %}- Para obtener más información sobre la autenticación bifactorial utilizando {% data variables.product.prodname_mobile %}, consulta las secciones "[Configurar {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) y [Autenticarte utilizando {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)". {% endif %} ## Instalar {% data variables.product.prodname_mobile %} @@ -38,7 +38,7 @@ Para instalar {% data variables.product.prodname_mobile %} para Android o iOS, c ## Administrar cuentas -You can be simultaneously signed into mobile with one personal account on {% data variables.product.prodname_dotcom_the_website %} and one personal account on {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre nuestros diversos productos, consulta la sección "[Productos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)". +Puedes estar firmado simultáneamente en un dispositivo móvil con una cuenta personal en {% data variables.product.prodname_dotcom_the_website %} y otra en {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre nuestros diversos productos, consulta la sección "[Productos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)". {% data reusables.mobile.push-notifications-on-ghes %} @@ -48,9 +48,9 @@ You can be simultaneously signed into mobile with one personal account on {% dat Debes instalar {% data variables.product.prodname_mobile %} 1.4 o posterior en tu dispositivo para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}. -Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} +Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. Para obtener más información, consulta la sección {% ifversion ghes %}"[Notas de lanzamiento](/enterprise-server/admin/release-notes)" y {% endif %}"[Administrar {% data variables.product.prodname_mobile %} par tu empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" en la documentación de {% data variables.product.prodname_ghe_server %}.{% else %}".{% endif %} -During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}. +Durante el beta de {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, debes estar firmado con una cuenta personal en {% data variables.product.prodname_dotcom_the_website %}. ### Agregar, cambiar o cerrar sesión en las cuentas diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md index 0fb6142b40..20cc3b0850 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md @@ -1,6 +1,6 @@ --- -title: Organizing information with collapsed sections -intro: You can streamline your Markdown by creating a collapsed section with the `
` tag. +title: Organizar información con secciones colapsadas +intro: Puedes optimizar tu lenguaje de marcado si creas una sección colapsada con la etiqueta `
`. versions: fpt: '*' ghes: '*' @@ -8,14 +8,14 @@ versions: ghec: '*' redirect_from: - /github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections -shortTitle: Collapsed sections +shortTitle: Secciones colapsadas --- -## Creating a collapsed section +## Crear una sección colapsada -You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section. +Puedes ocultar las secciones de tu lenguaje de marcado temporalmente si creas una sección colapsada que el lector pueda elegir desplegar. Por ejemplo, cuando incluyes detalles técnicas en un comentario de una propuesta, los cuales podrían no ser relevantes o de interés para todos los lectores, puedes ponerlos en una sección colapsada. -Any Markdown within the `
` block will be collapsed until the reader clicks {% octicon "triangle-right" aria-label="The right triange icon" %} to expand the details. Within the `
` block, use the `` tag to create a label to the right of {% octicon "triangle-right" aria-label="The right triange icon" %}. +Cualquier lenguaje de mrcado dentro del bloque `
` se colapsará hasta que el lector haga clic en {% octicon "triangle-right" aria-label="The right triange icon" %} para expandir los detalles. Dentro del bloque de `
`, utiliza la marca `` para crear una etiqueta a la derecha de {% octicon "triangle-right" aria-label="The right triange icon" %}. ```markdown
CLICK ME @@ -29,13 +29,13 @@ Any Markdown within the `
` block will be collapsed until the reader cli
```

-The Markdown will be collapsed by default. +El lenguaje de marcado se colapsará predeterminadamente. -![Rendered collapsed](/assets/images/help/writing/collapsed-section-view.png) +![Representación colapsada](/assets/images/help/writing/collapsed-section-view.png) -After a reader clicks {% octicon "triangle-right" aria-label="The right triange icon" %}, the details are expanded. +Después de que un lector hace clic en {% octicon "triangle-right" aria-label="The right triange icon" %}, los detalles se expandirán. -![Rendered open](/assets/images/help/writing/open-collapsed-section.png) +![Representación abierta](/assets/images/help/writing/open-collapsed-section.png) ## Leer más diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md index 6c813260f9..4828bd39e8 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md @@ -1,7 +1,7 @@ --- -title: Managing security settings for your organization -shortTitle: Manage security settings -intro: 'You can manage security settings and review the audit log{% ifversion ghec %}, compliance reports,{% endif %} and integrations for your organization.' +title: Administrar los ajustes de seguridad de tu organización +shortTitle: Administrar los ajustes de seguridad +intro: 'Puedes administrar los ajustes de seguridad y revisar la bitácora de auditoría{% ifversion ghec %}, reportes de cumplimiento,{% endif %} e integraciones de tu organización.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 4275eef176..7ae936c864 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -492,11 +492,11 @@ Para obtener más información, consulta la sección "[Administrar la publicaci ### Acciones de la categoría `org_secret_scanning_custom_pattern` -| Acción | Descripción | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Triggered when a custom pattern is published for secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)". | -| `actualización` | Triggered when changes to a custom pattern are saved for secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | -| `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | +| Acción | Descripción | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create (crear)` | Se activa cuando se publica un patrón personalizado para el escaneo de secretos en una organización. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)". | +| `actualización` | Se activa cuando se guardan los cambios a un patrón personalizado para el escaneo de secretos en una organización. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | +| `delete` | Se activa cuando se elimina un patrón personalizado desde un escaneo de secretos en una organización. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | {% endif %} ### Acciones de la categoría `organization_label` @@ -523,9 +523,9 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `package_version_published` | Se activa cuando se publica una versión del paquete. | | `package_version_deleted` | Se activa cuando se borra una versión de un paquete específico.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} -| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `package_deleted` | Se activa cuando se borra todo un paquete.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} | `package_version_restored` | Se activa cuando se borra una versión de un paquete específico.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} -| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `package_restored` | Se activa cuando se restablece todo un paquete.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} {% ifversion fpt or ghec %} @@ -690,11 +690,11 @@ Para obtener más información, consulta la sección "[Administrar la publicaci ### Acciones de la categoría `repository_secret_scanning_custom_pattern` -| Acción | Descripción | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Triggered when a custom pattern is published for secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)". | -| `actualización` | Triggered when changes to a custom pattern are saved for secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | -| `delete` | Triggered when a custom pattern is removed from secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | +| Acción | Descripción | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando se publica un patrón personalizado para el escaneo de secretos de un repositorio. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)". | +| `actualización` | Se activa cuando se guardan los cambios a un patrón personalizado para el escaneo de secretos en un repositorio. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | +| `delete` | Se activa cuando se elimina un patrón personalizado desde el escaneo de secretos de un repositorio. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | {% endif %}{% if secret-scanning-audit-log-custom-patterns %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index b190f87721..544f00ca44 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -123,7 +123,7 @@ Predeterminadamente, cuando creas una organización nueva, `GITHUB_TOKEN` solo t 1. Da clic en **Guardar** para aplicar la configuración. {% if allow-actions-to-approve-pr %} -### Preventing {% data variables.product.prodname_actions %} from {% if allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests +### Prevenir que {% data variables.product.prodname_actions %} {% if allow-actions-to-approve-pr-with-ent-repo %}cree o {% endif %}apruebe solicitudes de cambios {% data reusables.actions.workflow-pr-approval-permissions-intro %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md index 9b40bbf0af..463dd436a3 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md @@ -1,6 +1,6 @@ --- -title: Keeping your pull request in sync with the base branch -intro: 'After you open a pull request, you can update the head branch, which contains your changes, with any changes that have been made in the base branch.' +title: Mantener sincronizada tu solicitud de cambios en la rama base +intro: 'Después de que abres una solicitud de cambios, puedes actualizar la rama de encabezado, la cual contiene tus cambios con cualquier otro que se haya hecho en la rama base.' permissions: People with write permissions to the repository to which the head branch of the pull request belongs can update the head branch with changes that have been made in the base branch. versions: fpt: '*' @@ -9,45 +9,45 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Update the head branch +shortTitle: Actualizar la rama de encabezado --- -## About keeping your pull request in sync +## Acerca de mantener tu solicitud de cambios sincronizada -Before merging your pull requests, other changes may get merged into the base branch causing your pull request's head branch to be out of sync. Updating your pull request with the latest changes from the base branch can help catch problems prior to merging. +Antes de que fusiones tus solicitudes de cambios, podrían fusionarse otros cambios en la rama base, lo cual ocasionaría que tu rama de encabezado de la solicitud de cambios se desincronice. El actualizar tu solicitud de cambios con los últimos cambios de la rama base puede ayudarte a notar problemas antes de la fusión. -You can update a pull request's head branch from the command line or the pull request page. The **Update branch** button is displayed when all of these are true: +Puedes actualizar una rama de encabezado de una solicitud de cambios con la línea de comandos o en la página de la solicitud de cambios. Se mostrará el botón **Actualizar rama** cuando se cumpla con todo esto: -* There are no merge conflicts between the pull request branch and the base branch. -* The pull request branch is not up to date with the base branch. -* The base branch requires branches to be up to date before merging{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} or the setting to always suggest updating branches is enabled{% endif %}. +* Que no haya conflictos de fusión entre la rama de la solicitud de cambios y la rama base. +* Que la rama de la solicitud de cambios no esté actualizada con la rama base. +* Que la rama base requiera que las ramas estén actualizadas antes de fusionarlas{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} o que esté habilitada la configuración para que siempre se sugiera actualizar las ramas{% endif %}. Para obtener más información, consulta las secciones "[Requerir verificaciones de estado antes de fusionar](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}" y "[Adminsitrar las sugerencias para actualizar las ramas de la solicitud de cambios](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches){% endif %}". -If there are changes to the base branch that cause merge conflicts in your pull request branch, you will not be able to update the branch until all conflicts are resolved. For more information, see "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)." +Si existen cambios en la rama base que ocasiones conflictos de fusión en la rama de tu solicitud de cambios, no podrás actualizar la rama hasta que se resuelvan todos los conflictos. Para obtener más información, consulta la sección "[Acerca de los conflictos de fusión](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)". {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} -From the pull request page you can update your pull request's branch using a traditional merge or by rebasing. A traditional merge results in a merge commit that merges the base branch into the head branch of the pull request. Rebasing applies the changes from _your_ branch onto the latest version of the base branch. The result is a branch with a linear history, since no merge commit is created. +Desde la página de la solicitud de cambios, puedes actualizar la rama de tu solicitud de cambios utilizando una fusión tradicional o rebasando. Una fusión tradicional dará como resultado una confirmación de fusión que fusionará la rama base en la rama de encabezado de la solicitud de cambios. El rebase aplica los cambios desde _tu_ rama en la última versión de la rama base. El resultado es una rama con un historial linear, ya que no se crea ninguna confirmación de fusión. {% else %} -Updating your branch from the pull request page performs a traditional merge. The resulting merge commit merges the base branch into the head branch of the pull request. +El actualizar tu rama desde la página de solicitudes de cambio realizará una fusión tradicional. La confirmación de fusión resultante fusionará la rama base en la rama de encabezado de la solicitud de cambios. {% endif %} -## Updating your pull request branch +## Actualizar tu rama de solicitud de cambios {% data reusables.repositories.sidebar-pr %} -1. In the "Pull requests" list, click the pull request you'd like to update. +1. En la lista de "Solicitud de cambios", haz clic en la solicitud que te gustaría actualizar. {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} -1. In the merge section near the bottom of the page, you can: - - Click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png) - - Click the update branch drop down menu, click **Update with rebase**, and then click **Rebase branch** to update by rebasing on the base branch. ![Drop-down menu showing merge and rebase options](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png) +1. En la sección de fusión cerca de la parte inferior de la página, puedes: + - Hacer clic en **Actualizar rama** para realizar una fusión tradicional. ![Botón para actualizar la rama](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png) + - Haz clic en el menú desplegable de "actualizar rama", luego en **Actualizar con rebase** y luego en **Rebasar rama** para actualizar rebasando en la rama base. ![Menú desplegable que muestra las opciones de rebase y fusión](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png) {% else %} -1. In the merge section near the bottom of the page, click **Update branch** to perform a traditional merge. ![Botón para actualizar una rama](/assets/images/help/pull_requests/pull-request-update-branch.png) +1. En la sección de fusión cerca de la parte inferior de la página, haz clic en **Actualizar rama** para realizar una fusión tradicional. ![Botón para actualizar una rama](/assets/images/help/pull_requests/pull-request-update-branch.png) {% endif %} ## Leer más - "[Acerca de las solicitudes de extracción](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" -- "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)" +- "[Cambiar el estado de una solicitud de cambios](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)" - "[Confirmar cambios en una rama de la solicitud de extracción creada desde una bifurcación](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 461bb3da0c..7da1e0c05f 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.3' - ghae: issue-4651 + ghae: '*' ghec: '*' topics: - Repositories diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md b/translations/es-ES/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md index 683d0d8d12..58d8a3b4bb 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md @@ -32,4 +32,5 @@ Si creas una URL no válida usando los parámetros de consulta o si no tienen lo ## Leer más -- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating an issue from a URL query](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-url-query)" +- "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request/)" diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml index e203119371..86c54b26a6 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -51,7 +51,7 @@ sections: - "You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the \"Required approvals\" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see \"[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests).\"\n" - heading: 'Re-run failed or individual GitHub Actions jobs' notes: - - "You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see \"[Re-running workflows and jobs](/managing-workflow-runs/re-running-workflows-and-jobs).\"\n" + - "You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see \"[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs).\"\n" - heading: 'Dependency graph supports GitHub Actions' notes: - "The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the \"Used By\" control on the repository homepage. For more information, see \"[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).\"\n" @@ -133,7 +133,7 @@ sections: - "Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the \"Affected branches\" sidebar and in the alert timeline. You can hover over the analysis origin icon in the \"Affected branches\" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see \"[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins).\"\n" - "Lists of repositories owned by a user or organization now have an additional filter option, \"Templates\", making it easier to find template repositories.\n" - "GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the \"Display rich diff\" option. For more information, see \"[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files).\"\n" - - "New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see \"[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)\" and \"[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories).\"\n" + - "New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see \"[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)\" and \"[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories).\"\n" - "Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see \"[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists).\"\n" - "Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/).\n" - "Focusing or hovering over a label now displays the label description in a tooltip.\n" diff --git a/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml index b8da1e31db..35509a16db 100644 --- a/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml +++ b/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -21,14 +21,14 @@ sections: - | GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - heading: 'Dependency graph' notes: - | - Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." - heading: 'Dependabot alerts' notes: @@ -74,7 +74,7 @@ sections: - heading: 'Audit log accessible via REST API' notes: - | - You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." - heading: 'Expiration dates for personal access tokens' notes: @@ -135,7 +135,7 @@ sections: - heading: 'GitHub Actions' notes: - | - To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." - | The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. @@ -183,7 +183,7 @@ sections: - heading: 'Repositories' notes: - | - GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - | You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. diff --git a/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md b/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md index 7e671d4127..2c5aa40af5 100644 --- a/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md +++ b/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md @@ -1 +1 @@ -If you protect your personal account with two-factor authentication but do not know your password, you will not be able to follow these steps to recover your account. {% data variables.product.company_short %} can send a password reset email to a verified address associated with your account. For more information, see "[Updating your {% data variables.product.prodname_dotcom %} access credentials](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." +If you protect your personal account with two-factor authentication but do not know your password, you will not be able to follow these steps to recover your account. {% data variables.product.company_short %} puede enviar un correo de restablecimiento de contraseña a una dirección verificada que se haya asociado con tu cuenta. Para obtener más información, consulta la sección "[Actualizar tus credenciales de acceso a {% data variables.product.prodname_dotcom %}](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)". diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md index 8f4453f9fc..52b390e2dd 100644 --- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md @@ -1 +1 @@ -1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern**{% elsif ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. +1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publicar patrón**{% elsif ghes > 3.2 or ghae %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}. diff --git a/translations/es-ES/data/reusables/projects/project-description.md b/translations/es-ES/data/reusables/projects/project-description.md index cfe9fe5995..8b1abbf69b 100644 --- a/translations/es-ES/data/reusables/projects/project-description.md +++ b/translations/es-ES/data/reusables/projects/project-description.md @@ -1,10 +1,10 @@ -You can set your project's description and README to share the purpose of your project, provide instructions on how to use the project, and include any relevant links. +Puedes obtener la descripción y el README de tu proyecto para compartir su propósito, proporcionar instrucciones sobre cómo utilizarlo e incluir cualquier enlace relevante. {% data reusables.projects.project-settings %} -1. To add a short description to your project, under "Add a description", type your description in the text box and click **Save**. -1. To update your project's README, under "README", type your content in the text box. - - You can format your README using Markdown. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)". - - To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}. -1. To save changes to your README, click **Save**. +1. Para agregar una descripción corta de tu proyecto, debajo de "Agregar descripción", escribe la descripción en la caja de texto y haz clic en **Guardar**. +1. Para actualizar el README de tu proyecto, debajo de "README", teclea tu contenido en la caja de texto. + - Puedes formatear tu README utilizando lenguaje de marcado. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)". + - Para alternar entre la caja de texto y una vista previa de tus cambios, haz clic en {% octicon "eye" aria-label="The preview icon" %} o en {% octicon "pencil" aria-label="The edit icon" %}. +1. Para guardar los cambios en tu README, haz clic en **Ahorrar**. -You can view and make quick changes to your project description and README by navigating to your project and clicking {% octicon "sidebar-expand" aria-label="The sidebar icon" %} in the top right. +Puedes ver y hacer cambios rápidos a tu descripción de proyecto y archivo de README si navegas a tu proyecto y haces clic en {% octicon "sidebar-expand" aria-label="The sidebar icon" %} en la parte superior derecha. diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md index f0822b155d..d3b9fc170c 100644 --- a/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md +++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md @@ -1,3 +1,3 @@ {% data variables.product.product_name %} fusiona la solicitud de cambios de acuerdo con la estrategia de fusión configurada en la protección de rama una vez que todas las verificaciones de IC hayan pasado. -![Merge queue merging method](/assets/images/help/pull_requests/merge-queue-merging-method.png) \ No newline at end of file +![Método de fusión de cola de fusión](/assets/images/help/pull_requests/merge-queue-merging-method.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md b/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md index a2ce8b3790..b824cd4e77 100644 --- a/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md +++ b/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md @@ -1,5 +1,5 @@ {% note %} -**Nota**: Puedes confirmar tu estado de límite de tasa actual en cualquier momento. For more information, see "[Checking your rate limit status](/rest/overview/resources-in-the-rest-api#checking-your-rate-limit-status)." +**Nota**: Puedes confirmar tu estado de límite de tasa actual en cualquier momento. Para obtener más información, consulta la sección "[Verificar tu estado de límite de tasa](/rest/overview/resources-in-the-rest-api#checking-your-rate-limit-status)". {% endnote %} diff --git a/translations/es-ES/data/reusables/saml/saml-disabled-linked-identities-removed.md b/translations/es-ES/data/reusables/saml/saml-disabled-linked-identities-removed.md index 8b081e0688..b7048f0279 100644 --- a/translations/es-ES/data/reusables/saml/saml-disabled-linked-identities-removed.md +++ b/translations/es-ES/data/reusables/saml/saml-disabled-linked-identities-removed.md @@ -1 +1 @@ -When SAML SSO is disabled, all linked external identities are removed from {% data variables.product.product_name %}. +Cuando se inhabilita el SSO de SAML, todas las identidades externas enlazadas se eliminarán de {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md b/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md index 2d3121b0cd..b2a227ed3e 100644 --- a/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md +++ b/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md @@ -1,6 +1,6 @@ {% note %} -**Note:** The dry run feature is currently in beta and subject to change. +**Nota:** La característica de simulación se encuentra actualmente en beta y está sujeta a cambios. {% endnote %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md index 30a3d24ddb..ac1511cb43 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories shortTitle: Manage default branch name --- ## About management of the default branch name diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 6b10663dfe..d391247e97 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -80,6 +80,7 @@ For the overall list of included tools for each runner operating system, see the * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) +* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md) * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 0197320998..416130cfad 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -19,7 +19,9 @@ topics: {% ifversion ghec %} -Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. You can choose to allow members create and manage user accounts, or your enterprise can create and manage accounts for members. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication. +Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. + +You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication. ## Authentication methods for {% data variables.product.product_name %} diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md index ae2d06af75..7bafef913e 100644 --- a/translations/ja-JP/content/admin/index.md +++ b/translations/ja-JP/content/admin/index.md @@ -71,13 +71,13 @@ changelog: featuredLinks: guides: - '{% ifversion ghae %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}' + - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise + - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies - '{% ifversion ghae %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}' - '{% ifversion ghes %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}' - '{% ifversion ghes %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}' - '{% ifversion ghes %}/admin/overview/about-upgrades-to-new-releases{% endif %}' - '{% ifversion ghec %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise{% endif %}' - - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users{% endif %}' - - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise{% endif %}' - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise{% endif %}' - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise guideCards: diff --git a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md index fdb8e5b0b1..21cb0a0c2a 100644 --- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md @@ -32,18 +32,18 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ {% endif %} -Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion ghec %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %} +Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。 + +{% ifversion ghec %} +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +{% endif %} + +Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." {% ifversion ghec %} -Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. 特定の強制の選択肢は、設定によって異なります。概して、Enterprise アカウント内のすべての Organization に単一のポリシーを強制するか、Organization レベルでオーナーがポリシーを設定することを許可するかを選択できます。 For more information, see "[Setting policies for your enterprise](/admin/policies)." - {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -{% elsif ghes or ghae %} - -For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)." - {% endif %} ## About administration of your enterprise account @@ -78,7 +78,7 @@ If you use both {% data variables.product.prodname_ghe_cloud %} and {% data vari You can also connect the enterprise account on {% data variables.product.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} -{% data variables.product.prodname_ghe_cloud %} と {% data variables.product.prodname_ghe_server %} の違いについては、「[{% data variables.product.prodname_dotcom %} の製品](/get-started/learning-about-github/githubs-products)」を参照してください。 {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} +For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} {% endif %} diff --git a/translations/ja-JP/content/admin/overview/creating-an-enterprise-account.md b/translations/ja-JP/content/admin/overview/creating-an-enterprise-account.md index 1504a6c795..a87a2e8500 100644 --- a/translations/ja-JP/content/admin/overview/creating-an-enterprise-account.md +++ b/translations/ja-JP/content/admin/overview/creating-an-enterprise-account.md @@ -16,7 +16,7 @@ shortTitle: Create enterprise account {% data variables.product.prodname_ghe_cloud %} includes the option to create an enterprise account, which enables collaboration between multiple organizations and gives administrators a single point of visibility and management. 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。 -{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to move to invoicing. +{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you. An enterprise account is included in {% data variables.product.prodname_ghe_cloud %}, so creating one will not affect your bill. @@ -29,7 +29,10 @@ If the organization is connected to {% data variables.product.prodname_ghe_serve ## Creating an enterprise account on {% data variables.product.prodname_dotcom %} -To create an enterprise account on {% data variables.product.prodname_dotcom %}, your organization must be using {% data variables.product.prodname_ghe_cloud %} and paying by invoice. +To create an enterprise account, your organization must be using {% data variables.product.prodname_ghe_cloud %}. + +If you pay by invoice, you can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. If you do not currently pay by invoice, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you. + {% data reusables.organizations.billing-settings %} 1. Click **Upgrade to enterprise account**. diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md new file mode 100644 index 0000000000..ef0e9857c9 --- /dev/null +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md @@ -0,0 +1,30 @@ +--- +title: About enterprise policies +intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.' +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - Enterprise + - Policies +--- + +To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. + +{% data reusables.enterprise.about-policies %} + +For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise. + +By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." + +While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise. + +{% ifversion ghes %} +Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)." +{% endif %} + +## 参考リンク + +- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」 diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 0bc539958b..c87a62d3e2 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -13,6 +13,7 @@ topics: - Enterprise - Policies children: + - /about-enterprise-policies - /enforcing-repository-management-policies-in-your-enterprise - /enforcing-team-policies-in-your-enterprise - /enforcing-project-board-policies-in-your-enterprise diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index df96487115..ef0ea220af 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -53,7 +53,7 @@ Each user on {% data variables.product.product_location %} consumes a seat on yo {% endif %} -{% data reusables.billing.about-invoices-for-enterprises %} For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} {%- ifversion ghes %} - "[About per-user pricing](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)" diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index aa3e5d243c..e9eea5a2f7 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -17,7 +17,7 @@ shortTitle: View subscription & usage ## About billing for enterprise accounts -You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %} diff --git a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 9376b0455a..96ea2dffee 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -15,7 +15,7 @@ topics: - Secret scanning --- -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **ノート:** {% data variables.product.prodname_secret_scanning %}のカスタムパターンは現在ベータであり、変更されることがあります。 @@ -33,7 +33,7 @@ topics: {%- else %}各OrganizationもしくはEnterpriseアカウントに対して、そしてリポジトリごとに20のカスタムパターンをサポートします。 {%- endif %} -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **ノート:** ベータの間、{% data variables.product.prodname_secret_scanning %}のカスタムパターンの使用には多少の制限があります。 diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index ba0df5ca7c..4c6336457b 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1483,6 +1483,17 @@ The security advisory dataset also powers the GitHub {% data variables.product.p - この webhook を受信するには、{% data variables.product.prodname_github_apps %} に `contents` 権限が必要です。 +### webhook ペイロードオブジェクト + +| キー | 種類 | 説明 | +| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------- | +| `inputs` | `オブジェクト` | Inputs to the workflow. Each key represents the name of the input while it's value represents the value of that input. | +{% data reusables.webhooks.org_desc %} +| `ref` | `string` | The branch ref from which the workflow was run. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.sender_desc %} +| `workflow` | `string` | Relative path to the workflow file which contains the workflow. | + ### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 12fd94d5d6..68a2d83b78 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -56,21 +56,23 @@ Your organization's billing settings page allows you to manage settings like you Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." ### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} - {% note %} - -To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). - - {% endnote %} #### 1. Enterprise アカウントについて An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. 詳細は「[Enterprise アカウントについて](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)」を参照してください。 -#### 2. Enterprise アカウントに Organization を追加する + +#### 2. Creating an enterpise account + + {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." + + {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you. + +#### 3. Enterprise アカウントに Organization を追加する Enterprise アカウント内に、新しい Organization を作成して管理できます。 詳しい情報については「[EnterpriseへのOrganizationの追加](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)」を参照してください。 Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. -#### 3. Enterprise アカウントのプランおよび利用状況を表示する +#### 4. Enterprise アカウントのプランおよび利用状況を表示する You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." ## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 01e6944f05..f539f66032 100644 --- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -39,7 +39,7 @@ shortTitle: Enterprise Server trial 1. [Organization を作成します](/enterprise-server@latest/admin/user-management/creating-organizations)。 2. {% data variables.product.prodname_dotcom %} の基本的な使い方を学ぶには、次を参照してください: - - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) ウェブキャスト + - [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast - {% data variables.product.prodname_dotcom %} ガイドの [Understanding the {% data variables.product.prodname_dotcom %}flow](https://guides.github.com/introduction/flow/) - {% data variables.product.prodname_dotcom %} ガイドの [Hello World](https://guides.github.com/activities/hello-world/) - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)" diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 051403ceff..bb2ea6f466 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.3' - ghae: issue-4651 + ghae: '*' ghec: '*' topics: - Repositories diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md index b01fc3e351..4a282b2b54 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md @@ -32,4 +32,5 @@ shortTitle: Automate release forms ## 参考リンク -- 「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」 +- "[Creating an issue from a URL query](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-url-query)" +- "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request/)" diff --git a/translations/ja-JP/data/learning-tracks/admin.yml b/translations/ja-JP/data/learning-tracks/admin.yml index 6ef7226986..a7aa266e92 100644 --- a/translations/ja-JP/data/learning-tracks/admin.yml +++ b/translations/ja-JP/data/learning-tracks/admin.yml @@ -135,5 +135,4 @@ get_started_with_your_enterprise_account: - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise - - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise - - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise + - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml index 8bc6d66989..3559c76872 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml @@ -2,17 +2,17 @@ date: '2021-12-07' sections: security_fixes: - - Support bundles could include sensitive files if they met a specific set of conditions. - - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598). - - A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.0.21, 3.1.13, 3.2.5. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Updated February 17, 2022. + - 特定の条件群が満たされる場合に、Support Bundleにセンシティブなファイルが含まれることがあります。 + - 承認の際にユーザに表示される以上の権限が、GitHub Appのユーザ認証Webフローの間に付与されてしまうUIの表示ミスの脆弱性がGitHub Enterprise Serverで特定されました。この脆弱性は3.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、バージョン3.2.5、3.1.13、3.0.21で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、[CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)が割り当てられました。 + - GitHub Pagesのサイトをビルドする際に悪用されることがあるリモートコード実行の脆弱性が、GitHub Enterprise Serverで特定されました。この脆弱性は3.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.21、3.1.13、3.2.5で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、[CVE-2021-41599]（https://www.cve.org/CVERecord?id=CVE-2021-41599）が割り当てられました。2022年2月17日更新。 bugs: - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - A misconfiguration in the Management Console caused scheduling errors. - - Docker would hold log files open after a log rotation. - - GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments. + - '`ghe-config-apply`を実行すると、`/data/user/tmp/pages`における権限の問題のために失敗することがあります。' + - Management Consoleの設定ミスにより、スケジューリングのエラーが生じました。 + - Dockerが、ログのローテーション後にログファイルをオープンしたまま保持します。 + - pre-receiveフック環境において、GraphQLのリクエストがGITHUB_USER_IP変数を設定しませんでした。 changes: - - Clarifies explanation of Actions path-style in documentation. - - Updates support contact URLs to use the current support site, support.github.com. + - ドキュメンテーションでActionsのパススタイルの説明を明確化します。 + - サポートの連絡先URLが現在のサポートサイトであるsupport.github.comを使うよう更新。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/23.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/23.yml index 20a5d64a49..803af4fe05 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/23.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/23.yml @@ -6,7 +6,7 @@ sections: - Sanitize more secrets in the generated support bundles - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. + - '`ghe-config-apply`を実行すると、`/data/user/tmp/pages`における権限の問題のために失敗することがあります。' - The save button in management console was unreachable by scrolling in lower resolution browsers. - IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade. - Some webhook related jobs could generated large amount of logs. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/1.yml index afe3b771c2..d484d8c7b6 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/1.yml @@ -4,20 +4,20 @@ sections: security_fixes: - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/27118, https://github.com/github/enterprise2/pull/27110 {% endcomment %}' bugs: - - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26973, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'In a GitHub Enterprise Server clustering configuration, Dependency Graph settings could have been incorrectly applied. {% comment %} https://github.com/github/enterprise2/pull/26981, https://github.com/github/enterprise2/pull/26861 {% endcomment %}' - - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26988, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26994, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27083, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27116, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193182, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193303 {% endcomment %}' - - 'Using the API to disable Secret Scanning correctly disabled the property but incorrectly returned an HTTP 422 and an error message. {% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}' - - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}' - - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}' - - 'A user defined pattern created for Secret Scanning would continue getting scanned even after it was deleted. {% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}' + - 'カスタムのpre-receive フックが、制約の厳しすぎる仮想メモリもしくはCPU時間の制限のために失敗することがありました。{% comment %}https://github.com/github/enterprise2/pull/26973, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' + - 'GitHub Enterprise Serverのクラスタリング構成で、依存関係グラフの設定が不正確に適用されることがありました。{% comment %} https://github.com/github/enterprise2/pull/26981, https://github.com/github/enterprise2/pull/26861 {% endcomment %}' + - '`ghe-cleanup-settings`で既存のすべての設定を消去しようとすると、Management Consoleサービスの再起動に失敗しました。{% comment %} https://github.com/github/enterprise2/pull/26988, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' + - '`ghe-repl-teardown` でのレプリケーションのティアダウンの間に、Memcachedが再起動に失敗しました。{% comment %} https://github.com/github/enterprise2/pull/26994, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' + - '高負荷の間、上流のサービスが内部的なヘルスチェックに失敗した際に、ユーザがHTTPステータスコード503を受信することになります。{% comment %} https://github.com/github/enterprise2/pull/27083, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' + - 'pre-receiveフック環境が、Alpine上のBusyBoxからcatコマンドを呼び出すことが禁じられていました。{% comment %} https://github.com/github/enterprise2/pull/27116, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' + - 'プライマリのクラスタデータセンターからセカンダリのクラスタデータセンターへのフェイルオーバーは成功しますが、その後オリジナルのプライマリクラスタデータセンターへのフェイルバックがElasticsearchインデックスの昇格に失敗しました。{% comment %} https://github.com/github/github/pull/193182, https://github.com/github/github/pull/192447 {% endcomment %}' + - 'OrganizationのTeamsページの"Import teams"ボタンがHTTP 404を返しました。{% comment %} https://github.com/github/github/pull/193303 {% endcomment %}' + - 'APIを使用してSecret scanningを無効化すると、無効化は正しく行われますが、誤ってHTTP 422とエラーメッセージが返されました。{% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}' + - '場合によって、`Dormant users` ページを閲覧しようとしたGitHub Enterpriseの管理者が`502 Bad Gateway`もしくは`504 Gateway Timeout`レスポンスを受信しました。{% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}' + - '特定の高負荷状況において、`SynchronizePullRequestJob`ジョブ数の増大の結果として、パフォーマンスに負の影響がありました。{% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}' + - 'Secret scanning用に作成されたユーザ定義パターンが、削除されたあとにもスキャンされ続けます。{% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}' changes: - - 'GitHub Apps now set the Secret Scanning feature on a repository consistently with the API. {% comment %} https://github.com/github/github/pull/193456, https://github.com/github/github/pull/193125 {% endcomment %}' + - 'GitHub Appsは、APIと整合性を持ってSecret scanningの機能を設定するようになりました。{% comment %} https://github.com/github/github/pull/193456, https://github.com/github/github/pull/193125 {% endcomment %}' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/10.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/10.yml index 6cd466a996..8cfa876bc4 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/10.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/10.yml @@ -2,10 +2,10 @@ date: '2022-03-01' sections: security_fixes: - - "HIGH: An integer overflow vulnerability was identified in GitHub's markdown parser that could potentially lead to information leaks and RCE. This vulnerability was reported through the GitHub Bug Bounty program by Felix Wilhelm of Google's Project Zero and has been assigned CVE-2022-24724." + - "高: GitHubのMarkdownパーサーで、情報漏洩とRCEにつながる整数オーバーフローの脆弱性が特定されました。この脆弱性は、GoogleのProject ZeroのFelix WilhelmによってGitHub Bug Bountyプログラムを通じて報告され、CVE-2022-24724が割り当てられました。" bugs: - - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. - - 'OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.2/rest/reference/apps#check-an-authorization) API endpoint.' + - 高可用性レプリカのクロックがプライマリと同期していない場合、アップグレードが失敗することがありました。 + - '2020年9月1日以降に作成されたOAuthアプリケーションは、 [Check an Authorization](https://docs.github.com/en/enterprise-server@3.2/rest/reference/apps#check-an-authorization) API エンドポイントを使用できませんでした。' known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml index e0bba6aaf3..c57451df9c 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml @@ -21,9 +21,9 @@ sections: - '`ghe-migrator`を使う場合、もしくは{% data variables.product.prodname_dotcom_the_website %}からエクスポートする場合、データがエクスポート中に削除されると実行に長時間かかるエクスポートが失敗します。' - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - Links to inaccessible pages were removed. - - Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages. + - Web UIで2つのコミットの比較から別のところに移動すると、他のページにdiffが保持されます。 - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. - - 'The [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API endpoint would respond with an error when attempting to remove a member managed externally by a SCIM group.' + - '外部でSCIMグループにょって管理されているメンバーを削除しようとすると、[Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API エンドポイントがエラーを返します。' - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. - The "Site admin mode" link in the site footer did not change state when clicked. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml index d6625e0168..c9ec0b4e2d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml @@ -8,11 +8,11 @@ sections: - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run. - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. - - Creating an impersonation OAuth token using the Enterprise Administration REST API worked incorrectly when an integration matching the OAuth Application ID already existed. + - OAuth Application IDがマッチするインテグレーションが既に存在する場合、Enterprise Administration REST APIを使った偽装OAuthトークンの作成が正しく動作しませんでした。 changes: - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - - The {% data variables.product.prodname_codeql %} starter workflow no longer errors even if the default token permissions for {% data variables.product.prodname_actions %} are not used. + - '{% data variables.product.prodname_codeql %}スターターワークフローは、{% data variables.product.prodname_actions %}のためのデフォルトのトークンの権限が使われていない場合でも、エラーになりません。' - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml index bb94ea5348..0f07a09858 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml @@ -2,21 +2,21 @@ date: '2022-05-17' sections: security_fixes: - - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - '** 中: ** DNSサーバーからのUDPパケットを偽造できる攻撃者が1バイトのメモリオーバーライトを起こし、ワーカープロセスをクラッシュさせたり、その他の潜在的にダメージのある影響を及ぼせるような、nginxリゾルバのセキュリティ問題が特定されました。この脆弱性には[CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017)が割り当てられました。' + - '`actions/checkout@v2`及び`actions/checkout@v3`アクションが更新され、[Gitセキュリティ施行ブログポスト](https://github.blog/2022-04-12-git-security-vulnerability-announced/)でアナウンスされた新しい脆弱性に対処しました。' - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. - - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. - - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. - - Videos uploaded to issue comments would not be rendered properly. - - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. - - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + - 一部のクラスタトポロジーで、`ghe-cluster-status`コマンドが`/tmp`に空のディレクトリを残しました。 + - SNMPがsyslogに大量の`Cannot statfs`エラーメッセージを誤って記録しました。 + - SAML認証が設定され、ビルトインのフォールバックが有効化されたインスタンスで、ビルトインのユーザがログアウト語に生成されたページからサインインしようとすると、“login”ループに捕まってしまいます。 + - Issueコメントにアップロードされたビデオが適切にレンダリングされません。 + - SAML暗号化されたアサーションを利用する場合、一部のアサーションは正しくSSHキーを検証済みとしてマークしませんでした。 + - '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。' changes: - - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. - - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. - - Support bundles now include the row count of tables stored in MySQL. - - Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information. + - 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。 + - '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。' + - Support BundleにはMySQLに保存されたテーブルの行数が含まれるようになりました。 + - 依存関係グラフは脆弱性のデータなしで有効化できるようになり、使用されている依存関係とバージョンを見ることができるようになりました。{% data variables.product.prodname_github_connect %}を有効化せずに依存関係グラフを有効化しても、脆弱性の情報は提供され**ません**。 known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml index 22fea8de2b..e57401cbb5 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml @@ -2,18 +2,18 @@ date: '2021-10-28' sections: security_fixes: - - 'It was possible for cleartext passwords to end up in certain log files.' + - '平文のパスワードが特定のログファイルに残る可能性がありました。' - 'いくつかの既知の弱いSSH公開鍵が拒否リストに追加され、登録できなくなりました。加えて、弱いSSHキーを生成することが知られているGitKrakenのバージョン（7.6.x、7.7.x、8.0.0）による新しい公開鍵の登録がブロックされました。' - 'パッケージは最新のセキュリティバージョンにアップデートされました。' bugs: - - 'Restore might fail for enterprise server in clustering mode if orchestrator is not healthily.' - - 'Codespaces links were displayed in organization settings.' + - 'orchestratorが正常でない場合、クラスタリングモードのEnterpriseサーバーのリストアが失敗することがあります。' + - 'CodespacesのリンクがOrganizationの設定に表示されました。' - '多くのOrganizationのオーナーであるユーザは、アプリケーションの一部を使用できませんでした。' - - 'Fixed a link to https://docs.github.com.' + - 'https://docs.github.comへのリンクを修正しました。' changes: - - 'Browsing and job performance optimizations for repositories with many refs.' + - '多くのrefを持つリポジトリのブラウズ及びジョブのパフォーマンス最適化。' known_issues: - - After saving a new release on a repository, the `/releases` page shows a 500 error. A fix for this issue is expected to ship in 3.2.3. + - リポジトリで新しいリリースを保存したあと、`/releases`ページが500エラーを表示しました。この問題の修正は、3.2.3で出荷される予定です。 - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml index 4464bde745..92778dbba3 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml @@ -8,14 +8,14 @@ sections: - GitHub Actionsが有効化されている場合、`ghe-repl-start`もしくは`ghe-repl-status`を実行すると、データベースへの接続でエラーが返されることがあります。 - pre-receiveフックが`PATH`の未定義で失敗します。 - 'インスタンスが以前にレプリカとして設定されていた場合、`ghe-repl-setup`を実行すると`cannot create directory /data/user/elasticsearch: File exists`というエラーが返されます。' - - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' + - '`ghe-support-bundle`を実行すると、`integer expression expected`というエラーが返されます。' - '高可用性レプリカをセットアップした後、`ghe-repl-status`は`unexpected unclosed action in command`というエラーを出力に含めました。' - 大規模なクラスタ環境に置いて、一部のフロントエンドノードで認証バックエンドが利用できなくなることがあります。 - GHESクラスタにおいて、一部の重要なサービスがバックエンドノードで利用できないことがあります。 - - The repository permissions to the user returned by the `/repos` API would not return the full list. - - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. - - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. - - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. + - '`/repos` APIによってユーザに返されたリポジトリ権限は、完全なリストを返しません。' + - GraphQL スキーマの`Team`オブジェクトの`childTeams`接続は、一部の状況で誤った結果を生成しました。 + - 高可用性設定では、リポジトリのメンテナンスは成功した場合であっても常にstafftoolsで失敗があったと表示しました。 + - ユーザ定義のパターンは、 `package.json`あるいは`yarn.lock`といったファイル内のシークレットを検出しません。 changes: - '`ghe-cluster-suport-bundle`でクラスタSupport Bundleを作成する際の`gzip`圧縮の追加外部レイヤーは、デフォルトでオフになりました。この外部圧縮は、ghe-cluster-suport-bundle -c`コマンドラインオプションで適用できます。' - 体験を改善するためのモバイルアプリケーションのデータ収集についてユーザにリマインドするために、管理コンソールにテキストを追加しました。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml index b271685618..38cc45ebac 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml @@ -2,22 +2,22 @@ date: '2021-12-07' sections: security_fixes: - - Support bundles could include sensitive files if they met a specific set of conditions. - - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598). - - A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.0.21, 3.1.13, 3.2.5. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Updated February 17, 2022. + - 特定の条件群が満たされる場合に、Support Bundleにセンシティブなファイルが含まれることがあります。 + - 承認の際にユーザに表示される以上の権限が、GitHub Appのユーザ認証Webフローの間に付与されてしまうUIの表示ミスの脆弱性がGitHub Enterprise Serverで特定されました。この脆弱性は3.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、バージョン3.2.5、3.1.13、3.0.21で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、[CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)が割り当てられました。 + - GitHub Pagesのサイトをビルドする際に悪用されることがあるリモートコード実行の脆弱性が、GitHub Enterprise Serverで特定されました。この脆弱性は3.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.21、3.1.13、3.2.5で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、[CVE-2021-41599]（https://www.cve.org/CVERecord?id=CVE-2021-41599）が割り当てられました。2022年2月17日更新。 bugs: - - In some cases when Actions was not enabled, `ghe-support-bundle` reported an unexpected message `Unable to find MS SQL container.` - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - A misconfiguration in the Management Console caused scheduling errors. - - Docker would hold log files open after a log rotation. - - Migrations could get stuck due to incorrect handling of `blob_path` values that are not UTF-8 compatible. - - GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments. - - Pagination links on org audit logs would not persist query parameters. - - During a hotpatch, it was possible for duplicate hashes if a transition ran more than once. + - Actionsが有効化されていない場合に、一部のケースで`ghe-support-bundle`が予期しない`Unable to find MS SQL container`というメッセージを報告しました。 + - '`ghe-config-apply`を実行すると、`/data/user/tmp/pages`における権限の問題のために失敗することがあります。' + - Management Consoleの設定ミスにより、スケジューリングのエラーが生じました。 + - Dockerが、ログのローテーション後にログファイルをオープンしたまま保持します。 + - UTF-8互換ではない`blob_path`の値の誤った処理のため、移行が止まってしまうことがあります。 + - pre-receiveフック環境において、GraphQLのリクエストがGITHUB_USER_IP変数を設定しませんでした。 + - OrgのAudit log上のページネーションのリンクが、クエリパラメータを保持しません。 + - ホットパッチの際にトランザクションが複数回実行されると、ハッシュが重複する可能性があります。 changes: - - Clarifies explanation of Actions path-style in documentation. - - Updates support contact URLs to use the current support site, support.github.com. - - Additional troubleshooting provided when running `ghe-mssql-diagnostic`. + - ドキュメンテーションでActionsのパススタイルの説明を明確化します。 + - サポートの連絡先URLが現在のサポートサイトであるsupport.github.comを使うよう更新。 + - '`ghe-mssql-diagnostic`を実行する際に、追加のトラブルシューティングが提供されます。' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/7.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/7.yml index 3fb979602b..3dccabaad2 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/7.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/7.yml @@ -8,7 +8,7 @@ sections: bugs: - Actions self hosted runners would fail to self-update or run new jobs after upgrading from an older GHES installation. - Storage settings could not be validated when configuring MinIO as blob storage for GitHub Packages. - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. + - '`ghe-config-apply`を実行すると、`/data/user/tmp/pages`における権限の問題のために失敗することがあります。' - The save button in management console was unreachable by scrolling in lower resolution browsers. - IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade. - Some webhook related jobs could generated large amount of logs. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml index d021b2dab0..ce4cf5d297 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml @@ -5,15 +5,15 @@ sections: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - '`nginx`が手動で再起動されるまで、MySQLのシークレットのローテーション後にPagesが利用できなくなります。' - - Migrations could fail when {% data variables.product.prodname_actions %} was enabled. + - '{% data variables.product.prodname_actions %}が有効化されていると、移行に失敗することがあります。' - ISO 8601の日付でメンテナンススケジュールを設定すると、タイムゾーンがUTCに変換されないことから実際にスケジュールされる時間が一致しません。 - '`cloud-config.service`に関する誤ったエラーメッセージがコンソールに出力されます。' - '`ghe-cluster-each`を使ってホットパッチをインストールすると、バージョン番号が正しく更新されません。' - - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time. - - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group. + - webhookテーブルのクリーンアップジョブが同時に実行され、リソース競合とジョブの実行時間の増大を招くことがあります。 + - プライマリから実行された場合、レプリカ上の`ghe-repl-teardown`はレプリカをMSSQLの可用性グループから削除しません。 - CAS認証を使用し、"Reactivate suspended users"オプションが有効化されている場合、サスペンドされたユーザは自動的に際アクティベートされませんでした。 - - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly. - - A long-running database migration related to Security Alert settings could delay upgrade completion. + - ユーザへのメールベースの通知を検証済みあるいは承認されたドメイン上のメールに制限する機能が正常に動作しませんでした。 + - 長時間実行されるセキュリティアラート関連のデータベースの移行が、アップグレードの完了を遅延させることがあります。 changes: - GitHub Connectのデータ接続レコードに、アクティブ及び休眠ユーザ数と、設定された休眠期間が含まれるようになりました。 known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml index 702690ea4c..45a31548cd 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml @@ -2,14 +2,14 @@ date: '2022-02-17' sections: security_fixes: - - It was possible for a user to register a user or organization named "saml". + - ユーザが、"saml"というユーザもしくはOrganizationを登録することが可能でした。 - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. + - Azure Blob Storageが使われている場合、Management ConsoleでGitHub Packagesのストレージ設定を検証して保存することができませんでした。 + - 不正な文字セットの警告で、設定オプションのmssql.backup.cadenceによってghe-config-checkが失敗しました。 - memcachedから2^16以上のキーを取得する際のSystemStackError（スタックが深すぎる）を修正しました。 changes: - - Secret scanning will skip scanning ZIP and other archive files for secrets. + - Secret scaningがZIP及び他のアーカイブファイルでシークレットのスキャンをスキップしてしまいます。 known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml index f556a3d0fc..815a9f465e 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -5,74 +5,74 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **ノート:** {% data variables.product.product_location %}がリリース候補ビルドを実行している場合、ホットパッチでのアップグレードはできません。リリース候補はテスト環境でのみ実行することをおすすめします。 {% endnote %} - For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." + アップグレードの手順については「[{% data variables.product.prodname_ghe_server %}のアップグレード](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)　」を参照してください。 sections: features: - - heading: Security Manager role + heading: セキュリティマネージャーのロール notes: - | - Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access: + Organizationのオーナーは、Teamに対してセキュリティアラートの管理とリポジトリへのアクセス設定へのアクセスを許可できるようになりました。"security manager"のロールを任意のTeamに適用して、Teamのメンバーに以下のアクセスを付与できます。 - - Read access on all repositories in the organization. - - Write access on all security alerts in the organization. - - Access to the organization-level security tab. - - Write access on security settings at the organization level. - - Write access on security settings at the repository level. + - Organizationのすべてのリポジトリへの読み取りアクセス + - Organizationのすべてのセキュリティアラートへの書き込みアクセス + - Organizationレベルのセキュリティタブへのアクセス + - Organizationレベルのセキュリティ設定への書き込みアクセス + -リポジトリレベルのセキュリティ設定への書き込みアクセス - For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + 詳しい情報については「[Organizationのセキュリティマネージャーの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)」を参照してください。 - - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' + heading: 'GitHub Actions及びオートスケーリングのための新しいwebhookのための一過性のセルフホストランナー' notes: - | - {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + {% data variables.product.prodname_actions %}は、オートスケールするランナーを容易にするため、一過性（単一ジョブ）のセルフホストランナーと、新しい [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhookをサポートしました。 - Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management. + 一過性のランナーは、各ジョブがクリーンなイメージ上で実行されることが必要な、自己管理の環境に適しています。ジョブが実行されたあと、一過性のランナーは自動的に{% data variables.product.product_location %}から登録解除され、ジョブ後の管理が可能になります。 - You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. + 一過性のランナーを新しい`workflow_job` webhookと組み合わせて、{% data variables.product.prodname_actions %}のジョブリクエストに応じてセルフホストランナーを自動的にスケールさせることができます。 - For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + 詳しい情報については「[セルフホストランナーのオートスケーリング](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)」及び「[webhookイベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)」を参照してください。 - - heading: 'Dark high contrast theme' + heading: 'ダーク高コントラストテーマ' notes: - | - A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes. + 前面の要素と背景要素のコントラストを大きくしたダーク高コントラストテーマが{% data variables.product.prodname_ghe_server %} 3.3で利用できるようになりました。このリリースには、すべての{% data variables.product.company_short %}テーマに渡るカラーシステムの改善も含まれています。 - ![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif) + ![外見設定ページでのダークデフォルトテーマとダーク高コントラストの切り替えのアニメーション画像](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif) - For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + テーマの切り替えに関する詳しい情報については「[テーマ設定の管理](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)」を参照してください。 changes: - heading: 管理に関する変更 notes: - - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.' - - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."' - - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."' - - A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity. + - '{% data variables.product.prodname_ghe_server %} 3.3には、リポジトリのメンテナンスの改善、特に多くの到達不能なオブジェクトを含むリポジトリに対する改善が含まれます。{% data variables.product.prodname_ghe_server %} 3.3へのアップグレード後の最初のメンテナンスサイクルが完了するまでには、通常よりも長くかかるかもしれないことに注意してください。' + - '{% data variables.product.prodname_ghe_server %} 3.3には、地理的に分散したチームとCIインフラストラクチャのためのリポジトリキャッシュのパブリックベータが含まれています。このリポジトリキャッシュは、追加の地点で利用できる読み取りのみのリポジトリのコピーを保持するもので、クライアントがプライマリインスタンスから重複してGitのコンテンツをダウンロードすることを回避してくれます。詳しい情報については「[リポジトリのキャッシングについて](/admin/enterprise-management/caching-repositories/about-repository-caching)」を参照してください。' + - '{% data variables.product.prodname_ghe_server %} 3.3には、ユーザ偽装プロセスの改善が含まれています。偽装セッションには偽装の正当性が必要になり、アクションは偽装されたユーザとして行われたものとしてAudit logに記録され、偽装されたユーザには、Enterpriseの管理者によって偽装されたというメール通知が届きます。詳しい情報については「[ユーザの偽装](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)を参照してください。' + - Gitと{% data variables.product.prodname_actions %}のアクティビティに関連するイベントを含む、Audit logに公開されるイベントの増大を受けつけるために、新しいストリーム処理のサービスが追加されました。 - heading: トークンの変更 notes: - | - An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original. + 新しい個人アクセストークン及び既存の個人アクセストークンに、期限切れの期日を設定でいるようになりました。古いトークンが漏洩し、セキュリティを毀損することがないよう、個人アクセストークンには期限切れの期日を設定することを強くおすすめします。トークンのオーナーは、期限切れが近づいたトークンを更新する時期になるとメールを受信します。期限切れになったトークンは再生成することができ、ユーザはオリジナルと同じ属性を持つ重複したトークンを受け取ることになります。 - When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + 個人アクセストークンを{% data variables.product.company_short %} APIで使う場合、新しい`GitHub-Authentication-Token-Expiration`ヘッダがレスポンスに含まれます。これは、トークンの期限切れの期日を示します。詳しい情報については「[個人アクセストークンの作成](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 - - heading: 'Notifications changes' + heading: '通知の変更' notes: - - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.' + - 'ディスカッションからの通知メールのタイトルには`(Discussion #xx)`が含まれるようになったので、ディスカッションを参照するメールを認識してフィルタリングできます。' - heading: 'リポジトリの変更' notes: - - Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code. - - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. - - When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. - - You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers. - - When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)." - - A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + - パブリックリポジトリは、プライベート及びインターナルリポジトリのように名前の隣に`Public`というラベルが付くようになりました。この変更によって、パブリックリポジトリを特定し、誤ってプライベートなコードをコミットすることを避けるのが容易になります。 + - ブランチ選択メニューを使う際に正確なブランチ名を指定すると、マッチするブランチの最上位にその結果が現れるようになりました。以前は厳密にマッチしたブランチ名がリストの末尾に表示されることがありました。 + - 対応するオープンなPull Requestを持つブランチを表示する際に、{% data variables.product.prodname_ghe_server %}はPull Requestに直接リンクするようになりました。以前は、ブランチの比較を使って貢献するか、新しいPull Requestをオープンするためのプロンプトがありました。 + - ボタンをクリックして、ファイルの生の内容をクリップボードにコピーできるようになりました。以前は、生のファイルを開き、すべてを選択し、コピーしなければなりませんでした。ファイルの内容をコピーするには、ファイルにアクセスし、ツールバーの{% octicon "copy" aria-label="The copy icon" %}をクリックしてください。この機能は現在、一部のブラウザでのみ利用可能であることに注意してください。 + - 新しいリリースを作成する際に、タグをテキストフィールドで指定するのではなく、ドロップダウンセレクタを使ってタグを選択あるいは作成できるようになりました。詳しい情報については「[リポジトリのリリースの管理](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)」を参照してください。 + - 双方向のUnicodeテキストを含むファイルを表示する際に、警告が表示されるようになりました。双方向のUnicodeテキストは、ユーザインターフェースで表示されるのとは異なるように解釈あるいはコンパイルされることがあります。たとえば、非表示の双方向Unicode文字を使ってテキストファイルのセグメントをスワップさせることがでいいます。これらの文字の置き換えに関する詳しい情報については[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/)を参照してください。 - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - heading: 'Markdownの変更' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml index fa825092b6..fa6471c977 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml @@ -4,67 +4,67 @@ intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodn sections: features: - - heading: Security Manager role + heading: セキュリティマネージャーのロール notes: - | - Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access: + Organizationのオーナーは、Teamに対してセキュリティアラートの管理とリポジトリへのアクセス設定へのアクセスを許可できるようになりました。"security manager"のロールを任意のTeamに適用して、Teamのメンバーに以下のアクセスを付与できます。 - - Read access on all repositories in the organization. - - Write access on all security alerts in the organization. - - Access to the organization-level security tab. - - Write access on security settings at the organization level. - - Write access on security settings at the repository level. + - Organizationのすべてのリポジトリへの読み取りアクセス + - Organizationのすべてのセキュリティアラートへの書き込みアクセス + - Organizationレベルのセキュリティタブへのアクセス + - Organizationレベルのセキュリティ設定への書き込みアクセス + -リポジトリレベルのセキュリティ設定への書き込みアクセス - For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + 詳しい情報については「[Organizationのセキュリティマネージャーの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)」を参照してください。 - - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' + heading: 'GitHub Actions及びオートスケーリングのための新しいwebhookのための一過性のセルフホストランナー' notes: - | - {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + {% data variables.product.prodname_actions %}は、オートスケールするランナーを容易にするため、一過性（単一ジョブ）のセルフホストランナーと、新しい [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhookをサポートしました。 - Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management. + 一過性のランナーは、各ジョブがクリーンなイメージ上で実行されることが必要な、自己管理の環境に適しています。ジョブが実行されたあと、一過性のランナーは自動的に{% data variables.product.product_location %}から登録解除され、ジョブ後の管理が可能になります。 - You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. + 一過性のランナーを新しい`workflow_job` webhookと組み合わせて、{% data variables.product.prodname_actions %}のジョブリクエストに応じてセルフホストランナーを自動的にスケールさせることができます。 - For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + 詳しい情報については「[セルフホストランナーのオートスケーリング](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)」及び「[webhookイベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)」を参照してください。 - - heading: 'Dark high contrast theme' + heading: 'ダーク高コントラストテーマ' notes: - | - A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes. + 前面の要素と背景要素のコントラストを大きくしたダーク高コントラストテーマが{% data variables.product.prodname_ghe_server %} 3.3で利用できるようになりました。このリリースには、すべての{% data variables.product.company_short %}テーマに渡るカラーシステムの改善も含まれています。 - ![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif) + ![外見設定ページでのダークデフォルトテーマとダーク高コントラストの切り替えのアニメーション画像](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif) - For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + テーマの切り替えに関する詳しい情報については「[テーマ設定の管理](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)」を参照してください。 changes: - heading: 管理に関する変更 notes: - - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.' - - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."' - - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."' - - A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity. + - '{% data variables.product.prodname_ghe_server %} 3.3には、リポジトリのメンテナンスの改善、特に多くの到達不能なオブジェクトを含むリポジトリに対する改善が含まれます。{% data variables.product.prodname_ghe_server %} 3.3へのアップグレード後の最初のメンテナンスサイクルが完了するまでには、通常よりも長くかかるかもしれないことに注意してください。' + - '{% data variables.product.prodname_ghe_server %} 3.3には、地理的に分散したチームとCIインフラストラクチャのためのリポジトリキャッシュのパブリックベータが含まれています。このリポジトリキャッシュは、追加の地点で利用できる読み取りのみのリポジトリのコピーを保持するもので、クライアントがプライマリインスタンスから重複してGitのコンテンツをダウンロードすることを回避してくれます。詳しい情報については「[リポジトリのキャッシングについて](/admin/enterprise-management/caching-repositories/about-repository-caching)」を参照してください。' + - '{% data variables.product.prodname_ghe_server %} 3.3には、ユーザ偽装プロセスの改善が含まれています。偽装セッションには偽装の正当性が必要になり、アクションは偽装されたユーザとして行われたものとしてAudit logに記録され、偽装されたユーザには、Enterpriseの管理者によって偽装されたというメール通知が届きます。詳しい情報については「[ユーザの偽装](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)を参照してください。' + - Gitと{% data variables.product.prodname_actions %}のアクティビティに関連するイベントを含む、Audit logに公開されるイベントの増大を受けつけるために、新しいストリーム処理のサービスが追加されました。 - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] - heading: トークンの変更 notes: - | - An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original. + 新しい個人アクセストークン及び既存の個人アクセストークンに、期限切れの期日を設定でいるようになりました。古いトークンが漏洩し、セキュリティを毀損することがないよう、個人アクセストークンには期限切れの期日を設定することを強くおすすめします。トークンのオーナーは、期限切れが近づいたトークンを更新する時期になるとメールを受信します。期限切れになったトークンは再生成することができ、ユーザはオリジナルと同じ属性を持つ重複したトークンを受け取ることになります。 - When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + 個人アクセストークンを{% data variables.product.company_short %} APIで使う場合、新しい`GitHub-Authentication-Token-Expiration`ヘッダがレスポンスに含まれます。これは、トークンの期限切れの期日を示します。詳しい情報については「[個人アクセストークンの作成](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 - - heading: 'Notifications changes' + heading: '通知の変更' notes: - - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.' + - 'ディスカッションからの通知メールのタイトルには`(Discussion #xx)`が含まれるようになったので、ディスカッションを参照するメールを認識してフィルタリングできます。' - heading: 'リポジトリの変更' notes: - - Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code. - - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. - - When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. - - You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers. - - When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)." - - A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + - パブリックリポジトリは、プライベート及びインターナルリポジトリのように名前の隣に`Public`というラベルが付くようになりました。この変更によって、パブリックリポジトリを特定し、誤ってプライベートなコードをコミットすることを避けるのが容易になります。 + - ブランチ選択メニューを使う際に正確なブランチ名を指定すると、マッチするブランチの最上位にその結果が現れるようになりました。以前は厳密にマッチしたブランチ名がリストの末尾に表示されることがありました。 + - 対応するオープンなPull Requestを持つブランチを表示する際に、{% data variables.product.prodname_ghe_server %}はPull Requestに直接リンクするようになりました。以前は、ブランチの比較を使って貢献するか、新しいPull Requestをオープンするためのプロンプトがありました。 + - ボタンをクリックして、ファイルの生の内容をクリップボードにコピーできるようになりました。以前は、生のファイルを開き、すべてを選択し、コピーしなければなりませんでした。ファイルの内容をコピーするには、ファイルにアクセスし、ツールバーの{% octicon "copy" aria-label="The copy icon" %}をクリックしてください。この機能は現在、一部のブラウザでのみ利用可能であることに注意してください。 + - 新しいリリースを作成する際に、タグをテキストフィールドで指定するのではなく、ドロップダウンセレクタを使ってタグを選択あるいは作成できるようになりました。詳しい情報については「[リポジトリのリリースの管理](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)」を参照してください。 + - 双方向のUnicodeテキストを含むファイルを表示する際に、警告が表示されるようになりました。双方向のUnicodeテキストは、ユーザインターフェースで表示されるのとは異なるように解釈あるいはコンパイルされることがあります。たとえば、非表示の双方向Unicode文字を使ってテキストファイルのセグメントをスワップさせることがでいいます。これらの文字の置き換えに関する詳しい情報については[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/)を参照してください。 - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - heading: 'Markdownの変更' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/2.yml index 7cdeccb69d..d363d60321 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/2.yml @@ -13,7 +13,7 @@ sections: - Storage settings could not be validated when configuring MinIO as blob storage for GitHub Packages. - GitHub Actions storage settings could not be validated and saved in the Management Console when "Force Path Style" was selected. - Actions would be left in a stopped state after an update with maintenance mode set. - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. + - '`ghe-config-apply`を実行すると、`/data/user/tmp/pages`における権限の問題のために失敗することがあります。' - The save button in management console was unreachable by scrolling in lower resolution browsers. - IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade. - Some webhook related jobs could generated large amount of logs. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml index db55dc799f..56044ac71d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml @@ -6,15 +6,15 @@ sections: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - '`nginx`が手動で再起動されるまで、MySQLのシークレットのローテーション後にPagesが利用できなくなります。' - - Migrations could fail when {% data variables.product.prodname_actions %} was enabled. + - '{% data variables.product.prodname_actions %}が有効化されていると、移行に失敗することがあります。' - ISO 8601の日付でメンテナンススケジュールを設定すると、タイムゾーンがUTCに変換されないことから実際にスケジュールされる時間が一致しません。 - '`cloud-config.service`に関する誤ったエラーメッセージがコンソールに出力されます。' - '`ghe-cluster-each`を使ってホットパッチをインストールすると、バージョン番号が正しく更新されません。' - - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time. - - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group. - - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly. + - webhookテーブルのクリーンアップジョブが同時に実行され、リソース競合とジョブの実行時間の増大を招くことがあります。 + - プライマリから実行された場合、レプリカ上の`ghe-repl-teardown`はレプリカをMSSQLの可用性グループから削除しません。 + - ユーザへのメールベースの通知を検証済みあるいは承認されたドメイン上のメールに制限する機能が正常に動作しませんでした。 - CAS認証を使用し、"Reactivate suspended users"オプションが有効化されている場合、サスペンドされたユーザは自動的に際アクティベートされませんでした。 - - A long-running database migration related to Security Alert settings could delay upgrade completion. + - 長時間実行されるセキュリティアラート関連のデータベースの移行が、アップグレードの完了を遅延させることがあります。 changes: - GitHub Connectのデータ接続レコードに、アクティブ及び休眠ユーザ数と、設定された休眠期間が含まれるようになりました。 known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml index cbe3af6e8f..67953ecaa6 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml @@ -2,16 +2,16 @@ date: '2022-02-17' sections: security_fixes: - - It was possible for a user to register a user or organization named "saml". + - ユーザが、"saml"というユーザもしくはOrganizationを登録することが可能でした。 - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. + - Azure Blob Storageが使われている場合、Management ConsoleでGitHub Packagesのストレージ設定を検証して保存することができませんでした。 + - 不正な文字セットの警告で、設定オプションのmssql.backup.cadenceによってghe-config-checkが失敗しました。 - memcachedから2^16以上のキーを取得する際のSystemStackError（スタックが深すぎる）を修正しました。 - A number of select menus across the site rendered incorrectly and were not functional. changes: - Dependency Graph can now be enabled without vulnerability data, allowing customers to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling GitHub Connect will *not* provide vulnerability information. - - Secret scanning will skip scanning ZIP and other archive files for secrets. + - Secret scaningがZIP及び他のアーカイブファイルでシークレットのスキャンをスキップしてしまいます。 known_issues: - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command. - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/5.yml index c4f21997bb..45b5377770 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/5.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/5.yml @@ -2,9 +2,9 @@ date: '2022-03-01' sections: security_fixes: - - "HIGH: An integer overflow vulnerability was identified in GitHub's markdown parser that could potentially lead to information leaks and RCE. This vulnerability was reported through the GitHub Bug Bounty program by Felix Wilhelm of Google's Project Zero and has been assigned CVE-2022-24724." + - "高: GitHubのMarkdownパーサーで、情報漏洩とRCEにつながる整数オーバーフローの脆弱性が特定されました。この脆弱性は、GoogleのProject ZeroのFelix WilhelmによってGitHub Bug Bountyプログラムを通じて報告され、CVE-2022-24724が割り当てられました。" bugs: - - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. + - 高可用性レプリカのクロックがプライマリと同期していない場合、アップグレードが失敗することがありました。 - 'OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.3/rest/reference/apps#check-an-authorization) API endpoint.' known_issues: - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml index a390a4f554..a912e75cfd 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml @@ -2,23 +2,23 @@ date: '2022-05-17' sections: security_fixes: - - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - '** 中: ** DNSサーバーからのUDPパケットを偽造できる攻撃者が1バイトのメモリオーバーライトを起こし、ワーカープロセスをクラッシュさせたり、その他の潜在的にダメージのある影響を及ぼせるような、nginxリゾルバのセキュリティ問題が特定されました。この脆弱性には[CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017)が割り当てられました。' + - '`actions/checkout@v2`及び`actions/checkout@v3`アクションが更新され、[Gitセキュリティ施行ブログポスト](https://github.blog/2022-04-12-git-security-vulnerability-announced/)でアナウンスされた新しい脆弱性に対処しました。' - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - 一部のクラスタトポロジーで、`ghe-cluster-status`コマンドが`/tmp`に空のディレクトリを残しました。 - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog - - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - SAML認証が設定され、ビルトインのフォールバックが有効化されたインスタンスで、ビルトインのユーザがログアウト語に生成されたページからサインインしようとすると、“login”ループに捕まってしまいます。 - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. - - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. - - Videos uploaded to issue comments would not be rendered properly. + - SAML暗号化されたアサーションを利用する場合、一部のアサーションは正しくSSHキーを検証済みとしてマークしませんでした。 + - Issueコメントにアップロードされたビデオが適切にレンダリングされません。 - When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems. - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. - - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + - '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。' changes: - - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. - - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. - - Support bundles now include the row count of tables stored in MySQL. + - 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。 + - '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。' + - Support BundleにはMySQLに保存されたテーブルの行数が含まれるようになりました。 - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml index 637bc1f3ab..ba6a2bf393 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml @@ -2,27 +2,27 @@ date: '2022-05-17' sections: security_fixes: - - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - '** 中: ** DNSサーバーからのUDPパケットを偽造できる攻撃者が1バイトのメモリオーバーライトを起こし、ワーカープロセスをクラッシュさせたり、その他の潜在的にダメージのある影響を及ぼせるような、nginxリゾルバのセキュリティ問題が特定されました。この脆弱性には[CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017)が割り当てられました。' + - '`actions/checkout@v2`及び`actions/checkout@v3`アクションが更新され、[Gitセキュリティ施行ブログポスト](https://github.blog/2022-04-12-git-security-vulnerability-announced/)でアナウンスされた新しい脆弱性に対処しました。' - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. - - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - 一部のクラスタトポロジーで、`ghe-cluster-status`コマンドが`/tmp`に空のディレクトリを残しました。 + - SNMPがsyslogに大量の`Cannot statfs`エラーメッセージを誤って記録しました。 - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect. - LDAP users with an underscore character (`_`) in their user names can now login successfully. - - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - SAML認証が設定され、ビルトインのフォールバックが有効化されたインスタンスで、ビルトインのユーザがログアウト語に生成されたページからサインインしようとすると、“login”ループに捕まってしまいます。 - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error. - Character key shortcut preferences weren't respected. - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. - - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. - - Videos uploaded to issue comments would not be rendered properly. + - SAML暗号化されたアサーションを利用する場合、一部のアサーションは正しくSSHキーを検証済みとしてマークしませんでした。 + - Issueコメントにアップロードされたビデオが適切にレンダリングされません。 - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. - - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + - '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。' changes: - - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。 - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete. - - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. - - Support bundles now include the row count of tables stored in MySQL. + - '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。' + - Support BundleにはMySQLに保存されたテーブルの行数が含まれるようになりました。 - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml index 53671dabd3..c087cf26d0 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -5,11 +5,11 @@ deprecated: false intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **ノート:** {% data variables.product.product_location %}がリリース候補ビルドを実行している場合、ホットパッチでのアップグレードはできません。リリース候補はテスト環境でのみ実行することをおすすめします。 {% endnote %} - For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." + アップグレードの手順については「[{% data variables.product.prodname_ghe_server %}のアップグレード](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)　」を参照してください。 sections: features: - @@ -122,7 +122,7 @@ sections: heading: Re-run failed or individual GitHub Actions jobs notes: - | - You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/managing-workflow-runs/re-running-workflows-and-jobs)." + You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - heading: Dependency graph supports GitHub Actions notes: @@ -313,7 +313,7 @@ sections: - | GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories)." + New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." - | Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." - | diff --git a/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml index 40645a176d..02f8fa03e4 100644 --- a/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml +++ b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -23,14 +23,14 @@ sections: - | GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - heading: '依存関係グラフ' notes: - | - Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." - heading: 'Dependabotアラート' notes: @@ -76,7 +76,7 @@ sections: heading: 'Audit log accessible via REST API' notes: - | - You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." - heading: 'Expiration dates for personal access tokens' notes: @@ -134,7 +134,7 @@ sections: heading: 'GitHub Actions' notes: - | - To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." - | The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. @@ -164,7 +164,7 @@ sections: - | You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." - | - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + ブランチ選択メニューを使う際に正確なブランチ名を指定すると、マッチするブランチの最上位にその結果が現れるようになりました。以前は厳密にマッチしたブランチ名がリストの末尾に表示されることがありました。 - | When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. - | @@ -175,7 +175,7 @@ sections: heading: 'リポジトリ' notes: - | - GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - | You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. - diff --git a/translations/ja-JP/data/reusables/enterprise/about-policies.md b/translations/ja-JP/data/reusables/enterprise/about-policies.md new file mode 100644 index 0000000000..7fd5303231 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise/about-policies.md @@ -0,0 +1 @@ +Each enterprise policy controls the options available for a policy at the organization level. You can choose to not enforce a policy, which allows organization owners to configure the policy for the organization, or you can choose from a set of options to enforce for all organizations owned by your enterprise. \ No newline at end of file diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index 8b89a92b7a..698b07d89a 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -36,6 +36,7 @@ search: homepage: explore_by_product: 製品で調べる version_picker: バージョン + description: Help for wherever you are on your GitHub journey. toc: getting_started: はじめましょう popular: 人気 diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 51f384d8af..ef70e2e6bd 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,6 +1,6 @@ --- -title: Setting up and managing your personal account on GitHub -intro: 'You can manage settings for your personal account on {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.' +title: Configurar e gerenciar sua conta pessoal no GitHub +intro: 'Você pode gerenciar as configurações da sua conta pessoal em {% data variables.product.prodname_dotcom %}, incluindo preferências de e-mail, acesso do colaborador a repositórios pessoais e associações da organização.' shortTitle: Contas pessoais redirect_from: - /categories/setting-up-and-managing-your-github-user-account diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index f097f1bad9..b58e9077a4 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -1,5 +1,5 @@ --- -title: Maintaining ownership continuity of your personal account's repositories +title: Manter a continuidade da propriedade dos repositórios da sua conta pessoal intro: Você pode convidar alguém para gerenciar seus repositórios pertencentes ao usuário se você não for capaz de fazê-lo. versions: fpt: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 6d543bdcb7..9a60a5a5a9 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -77,10 +77,10 @@ Após alteração do nome de usuário, os links para sua página de perfil anter {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %} -3. In the "Change username" section, click **Change username**. ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} -4. Leia os avisos sobre a mudança de seu nome de usuário. If you still want to change your username, click **I understand, let's change my username**. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-username-warning-button.png) +3. Na seção "Alterar nome de usuário", clique em **Alterar nome de usuário**. ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} +4. Leia os avisos sobre a mudança de seu nome de usuário. Se você ainda quiser alterar seu nome de usuário, clique em **Eu entendo, vamos alterar o meu nome de usuário**. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-username-warning-button.png) 5. Digite um novo nome de usuário. ![Campo New Username (Novo nome de usuário)](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. If the username you've chosen is available, click **Change my username**. Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-my-username-button.png) +6. Se o nome de usuário que você escolheu estiver disponível, clique em **Alterar meu nome de usuário**. Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-my-username-button.png) {% endif %} ## Leia mais diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md index a8c500b5ea..3cfa67307e 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md @@ -49,7 +49,7 @@ Você também pode converter sua conta pessoal diretamente em uma organização. 2. [Deixe qualquer organização](/articles/removing-yourself-from-an-organization) a conta pessoal que você está convertendo começou a participar. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %} -5. Under "Transform account", click **Turn into an organization**. ![Botão de conversão da organização](/assets/images/help/settings/convert-to-organization.png) +5. Em "Transformar conta", clique em **Transformar em uma organização**. ![Botão de conversão da organização](/assets/images/help/settings/convert-to-organization.png) 6. Na caixa de diálogo Account Transformation Warning (Aviso de transformação da conta), revise e confirme a conversão. Observe que as informações nessa caixa são as mesmas do aviso no início deste artigo. ![Aviso de conversão](/assets/images/help/organizations/organization-account-transformation-warning.png) 7. Na página "Transform your user into an organization" (Transformar usuário em uma organização), em "Choose an organization owner" (Escolher um proprietário da organização), escolha a conta pessoal secundária que você criou na seção anterior ou outro usuário em que confia para gerenciar a organização. ![Página Add organization owner (Adicionar proprietário da organização)](/assets/images/help/organizations/organization-add-owner.png) 8. Escolha a assinatura da nova organização e insira as informações de cobrança se solicitado. diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md index bd6a186b84..6ad4a153fd 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: Deleting your personal account +title: Excluindo sua conta pessoal intro: 'Você pode excluir sua conta pessoal em {% data variables.product.product_name %} a qualquer momento.' redirect_from: - /articles/deleting-a-user-account diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md index 21ebe854d2..5ff2a78c01 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md @@ -1,5 +1,5 @@ --- -title: Managing access to your personal account's project boards +title: Gerenciando o acesso aos quadros de projetos da sua conta pessoal intro: 'Como proprietário de quadro de projeto, você pode adicionar ou remover um colaborador e personalizar as permissões dele em um quadro de projeto.' redirect_from: - /articles/managing-project-boards-in-your-repository-or-organization diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md index 5c3e0ecf1a..0fce2b12f6 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: Managing security and analysis settings for your personal account +title: Gerenciar as configurações de segurança e análise para a sua conta pessoal intro: 'Você pode controlar recursos que protegem e analisam o código nos seus projetos no {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md index 290b69f520..343f4cb2bc 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories shortTitle: Gerenciar nome do branch padrão --- diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md index 00fb0fc2c0..559408d40b 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md @@ -1,5 +1,5 @@ --- -title: Merging multiple personal accounts +title: Fazendo merge de várias contas pessoais intro: 'Se você tem contas separadas para o trabalho e uso pessoal, é possível fazer merge das contas.' redirect_from: - /articles/can-i-merge-two-accounts diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md index d0ce67fb2d..3b151987c6 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -1,5 +1,5 @@ --- -title: Permission levels for a personal account repository +title: Níveis de permissão para o repositório de uma conta pessoal intro: 'Um repositório pertencente a uma conta pessoal tem dois níveis de permissão: o proprietário e os colaboradores do repositório.' redirect_from: - /articles/permission-levels-for-a-user-account-repository diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md index 2ef7b1517a..d994d00525 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md @@ -1,5 +1,5 @@ --- -title: Permission levels for a project board owned by a personal account +title: Níveis de permissão para um quadro de projeto pertencente a uma conta pessoal intro: 'Um quadro de projeto pertencente a uma conta pessoal tem dois níveis de permissão: o proprietário e colaboradores do quadro do projeto.' redirect_from: - /articles/permission-levels-for-user-owned-project-boards diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md index 443eb48166..96150c8ae4 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -244,7 +244,7 @@ steps: - run: pip test ``` -By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. Para obter mais informações, consulte "[Armazenando em cache as dependências de pacotes](https://github.com/actions/setup-python#caching-packages-dependencies)" no README do `setup-python`. +Por padrão, a ação `setup-python` busca o arquivo de dependência (`requirements.txt` para pip `Pipfile.lock` para pipenv ou `poetry.lock` para poetry) em todo o repositório. Para obter mais informações, consulte "[Armazenando em cache as dependências de pacotes](https://github.com/actions/setup-python#caching-packages-dependencies)" no README do `setup-python`. Se você tiver um requisito personalizado ou precisar de melhores controles para cache, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu acima, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip) no repositório de ação `cache`. diff --git a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md index 85942e30a9..7374813b7b 100644 --- a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -156,7 +156,7 @@ Você também pode criar um aplicativo que usa webhooks de status de implantaç ## Escolhendo um corredor -Você pode executar seu fluxo de trabalho de implantação em executores hospedados em {% data variables.product.company_short %} ou em executores auto-hospedados. O tráfego dos executores hospedados em {% data variables.product.company_short %} pode vir de uma [ampla gama de endereços de rede](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. Para superar isso, você pode hospedar seus próprios executores. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Sobre executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)." +Você pode executar seu fluxo de trabalho de implantação em executores hospedados em {% data variables.product.company_short %} ou em executores auto-hospedados. O tráfego dos executores hospedados em {% data variables.product.company_short %} pode vir de uma [ampla gama de endereços de rede](/rest/reference/meta#get-github-meta-information). Se você estiver fazendo a implantação em um ambiente interno e sua empresa restringir o tráfego externo em redes privadas, os fluxos de trabalho de {% data variables.product.prodname_actions %} em execução em executores hospedados em {% data variables.product.company_short %} podem não conseguir comunicar-se com seus serviços ou recursos internos. Para superar isso, você pode hospedar seus próprios executores. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Sobre executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)." {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md index 1662c1c12d..417fea7e16 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -12,7 +12,7 @@ topics: ## Sobre o {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} melhora {% data variables.product.product_name %}, o que permite que {% data variables.product.product_location %} se beneficie do poder de {% data variables.product.prodname_dotcom_the_website %} de maneira limitada. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. +{% data variables.product.prodname_github_connect %} melhora {% data variables.product.product_name %}, o que permite que {% data variables.product.product_location %} se beneficie do poder de {% data variables.product.prodname_dotcom_the_website %} de maneira limitada. Depois que você habilitar {% data variables.product.prodname_github_connect %}, você pode habilitar recursos e fluxos de trabalho adicionais que dependem de {% data variables.product.prodname_dotcom_the_website %} como, por exemplo, {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} para vulnerabilidades de segurança que são monitoradas no {% data variables.product.prodname_advisory_database %}{% else %}, o que permite que os usuários usem ações com base na comunidade de {% data variables.product.prodname_dotcom_the_website %} nos seus arquivos de fluxo de trabalho{% endif %}. {% data variables.product.prodname_github_connect %} não abre {% data variables.product.product_location %} para o público na internet. Nenhum dos dados privados da sua empresa está exposto os usuários de {% data variables.product.prodname_dotcom_the_website %}. Em vez disso, {% data variables.product.prodname_github_connect %} transmite apenas os dados limitados necessários para os recursos individuais que você optar por habilitar. A menos que você habilite a sincronização de licença, nenhum dado pessoal será transmitido por {% data variables.product.prodname_github_connect %}. Para obter mais informações sobre quais dados são transmitidos por {% data variables.product.prodname_github_connect %}, consulte "[Transmissão de dados para o {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)". @@ -28,7 +28,7 @@ Após configurar a conexão entre {% data variables.product.product_location %} | Funcionalidade | Descrição | Mais informações | | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronização automática da licença do usuário | Gerencie o uso da licença entre as suas implantações de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuários de {% data variables.product.product_location %} para {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} +| Sincronização automática da licença do usuário | Gerencie o uso da licença entre as suas implantações de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuários de {% data variables.product.product_location %} para {% data variables.product.prodname_ghe_cloud %}. | "[Habilitando a sincronização automática de licença de usuário para sua empresa](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} | {% data variables.product.prodname_dependabot %} | Permite aos usuários encontrar e corrigir vulnerabilidades nas dependências do código. | "[Habilitando {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} | Ações de {% data variables.product.prodname_dotcom_the_website %} | Permitir que os usuários usem ações de {% data variables.product.prodname_dotcom_the_website %} em arquivos de fluxo de trabalho. | "[Hbilitando o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} | {% data variables.product.prodname_server_statistics %} | Analise os seus próprios dados agregados do servidor do GitHub Enterprise e ajude-nos a melhorar os produtos do GitHub. | "[Habilitando {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 13b05b9c38..098f824b1b 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -64,7 +64,7 @@ Após habilitar {% data variables.product.prodname_dependabot_alerts %}, você p {% endnote %} -By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}. +Por padrão, os executores de {% data variables.product.prodname_actions %} usados por {% data variables.product.prodname_dependabot %} precisam de acesso à internet para fazer o download dos pacotes atualizados de gerentes de pacotes upstream. Para {% data variables.product.prodname_dependabot_updates %} alimentado por {% data variables.product.prodname_github_connect %}, o acesso à internet fornece aos seus executores um token que permite acesso a dependências e consultorias hospedadas em {% data variables.product.prodname_dotcom_the_website %}. Com {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} cria automaticamente pull requests para atualizar dependências de duas maneiras. @@ -127,6 +127,6 @@ Antes de habilitar {% data variables.product.prodname_dependabot_updates %}, voc Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, você também deve considerar configurar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Este recurso permite aos desenvolvedores corrigir a vulnerabilidades nas suas dependências. Para obter mais informações, consulte "[Gerenciar executores auto-hospedados para {% data variables.product.prodname_dependabot_updates %} na sua empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates). " -If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)." +Se você precisar de segurança reforçada, recomendamos configurar {% data variables.product.prodname_dependabot %} para usar registros privados. Para obter mais informações, consulte "[Gerenciando segredos criptografados para {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)". {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 8238abc58e..1cbde3fdfb 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -21,7 +21,7 @@ topics: Os proprietários das empresas em {% data variables.product.product_name %} podem controlar os requisitos de autenticação e acesso aos recursos da empresa. -You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. Se você permitir que os integrantes gerenciem suas próprias contas, você também pode configurar a autenticação SAML para aumentar a segurança e centralizar a identidade e o acesso dos aplicativos web que sua equipe usa. Se você optar por gerenciar as contas de usuário dos seus integrantes, será necessário configurar a autenticação SAML. +Você pode optar por permitir que os integrantes criem e gerenciem contas de usuário, ou sua empresa pode criar e gerenciar contas para integrantes com {% data variables.product.prodname_emus %}. Se você permitir que os integrantes gerenciem suas próprias contas, você também pode configurar a autenticação SAML para aumentar a segurança e centralizar a identidade e o acesso dos aplicativos web que sua equipe usa. Se você optar por gerenciar as contas de usuário dos seus integrantes, será necessário configurar a autenticação SAML. ## Métodos de autenticação para {% data variables.product.product_name %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md index b99c55dcbc..d65758a588 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md @@ -19,7 +19,7 @@ topics: Para usar o logon único SAML (SSO) para autenticação em {% data variables.product.product_name %}, você deve configurar seu provedor de identidade externo do SAML (IdP) e {% ifversion ghes %}{% data variables.product.product_location %}{% elsif ghec %}sua empresa ou organização em {% data variables.product.product_location %}{% elsif ghae %}sua empresa em {% data variables.product.product_name %}{% endif %}. Em uma configuração do SAML, as funções de {% data variables.product.product_name %} como um provedor de serviço do SAML (SP). -Você deve inserir valores únicos do IdP do seu SAML ao configurar o SAML SSO para {% data variables.product.product_name %}, e você também deve inserir valores únicos de {% data variables.product.product_name %} no seu IdP. For more information about the configuration of SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise){% ifversion ghes or ghae %}{% elsif ghec %}" or "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization){% endif %}." +Você deve inserir valores únicos do IdP do seu SAML ao configurar o SAML SSO para {% data variables.product.product_name %}, e você também deve inserir valores únicos de {% data variables.product.product_name %} no seu IdP. Para obter mais informações sobre a configuração do SAML SSO para {% data variables.product.product_name %}, consulte "[Configurando o logon únic SAML para a sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise){% ifversion ghes or ghae %}{% elsif ghec %}" ou "[Habilitando e testando o logon único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization){% endif %}." ## Metadados SAML @@ -80,9 +80,9 @@ Os seguintes atributos o SAML estão disponíveis para {% data variables.product | `NameID` | Sim | Identificador de usuário persistente. Qualquer formato de identificador de nome persistente pode ser usado. {% ifversion ghec %}Se você usa uma empresa com {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} irá normalizar o elemento `NameID` para usar como um nome de usuário, a menos que seja fornecida uma das declarações alternativas. Para obter mais informações, consulte "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". | | `SessionNotOnOrAfter` | Não | A data que {% data variables.product.product_name %} invalida a sessão associada. Após a invalidação, a pessoa deve efetuar a autenticação novamente para acessar {% ifversion ghec or ghae %}os recursos da sua empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Duração da sessão e fim do tempo](#session-duration-and-timeout)". | {%- ifversion ghes or ghae %} -| `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Qualquer outro valor ou um valor inexistente irá rebaixar a conta e remover o acesso administrativo. | | `username` | Não | O nome de usuário para {% data variables.product.product_location %}. | +| `administrator` | Nçao | Quando o valor for `verdadeiro`, {% data variables.product.product_name %} promoverá automaticamente o usuário para ser um {% ifversion ghes %}administrador de site{% elsif ghae %}proprietário empresarial{% endif %}. Qualquer outro valor ou um valor inexistente irá rebaixar a conta e remover o acesso administrativo. | | `username` | Não | O nome de usuário para {% data variables.product.product_location %}. | {%- endif %} -| `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. | | `emails` | No | The email addresses for the user.{% ifversion ghes or ghae %} You can specify more than one address.{% endif %}{% ifversion ghec or ghes %} If you sync license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} uses `emails` to identify unique users across products. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} | | `public_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} public SSH keys for the user. You can specify more than one key. | | `gpg_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} GPG keys for the user. You can specify more than one key. | +| `full_name` | Não | {% ifversion ghec %}Se você configurar um SAML SSO para uma empresa e usar {% data variables.product.prodname_emus %}, o{% else %}O{% endif %} nome completo do usuário a ser exibido na página de perfil do usuário. | | `emails` | Nçao | O endereço de e-mail para o usuário.{% ifversion ghes or ghae %} Você pode especificar mais de um endereço.{% endif %}{% ifversion ghec or ghes %} Se você sincronizar o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} usará `e-mails` para identificar usuários únicos nos produtos. Para obter mais informações, consulte "[Sincronizar o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} | | `public_keys` | Não | {% ifversion ghec %}Se você configurar o SAML SSO para uma empresa e usar {% data variables.product.prodname_emus %}, a{% else %}As{% endif %} chaves SSH públicas para o usuário. Você pode especificar mais de uma chave. | | `gpg_keys` | Não | {% ifversion ghec %}Se você configurar o SSO SAML para uma empresa e usar {% data variables.product.prodname_emus %}, as{% else %}As{% endif %} chaves GPG para o usuário. Você pode especificar mais de uma chave. | Para especificar mais de um valor para um atributo, use múltiplos elementos de ``. @@ -128,7 +128,7 @@ Para especificar mais de um valor para um atributo, use múltiplos elementos de ## Duração da sessão e tempo limite -Para impedir que uma pessoa efetue a autenticação com o seu IdP e permaneça indefinidamente autorizada, {% data variables.product.product_name %} invalida periodicamente a sessão para cada conta de usuário com acesso aos {% ifversion ghec or ghae %} recursos da sua empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. Depois da invalidação, a pessoa deverá efetuar a autenticação com seu IdP novamente. By default, if your IdP does not assert a value for the `SessionNotOnOrAfter` attribute, {% data variables.product.product_name %} invalidates a session {% ifversion ghec %}24 hours{% elsif ghes or ghae %}one week{% endif %} after successful authentication with your IdP. +Para impedir que uma pessoa efetue a autenticação com o seu IdP e permaneça indefinidamente autorizada, {% data variables.product.product_name %} invalida periodicamente a sessão para cada conta de usuário com acesso aos {% ifversion ghec or ghae %} recursos da sua empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. Depois da invalidação, a pessoa deverá efetuar a autenticação com seu IdP novamente. Por padrão, se o seu IdP não verificar um valor para o atributo `SessionNotOnOrAfter`, {% data variables.product.product_name %} invalida uma sessão {% ifversion ghec %}24 horas{% elsif ghes or ghae %}uma semana{% endif %} após a autenticação bem-sucedida com seu IdP. Para personalizar a duração da sessão, talvez você possa definir o valor do atributo `SessionNotOnOrAfter` no seu IdP. Se você definir um valor em menos de 24 horas, {% data variables.product.product_name %} poderá solicitar a autenticação das pessoas toda vez que {% data variables.product.product_name %} iniciar um redirecionamento. diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 70770a1481..a90126e82e 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -829,19 +829,19 @@ topics: ### ações da categoria `protected_branch` -| Ação | Descrição | -| ---------------------------------------- | ---------------------------------------------------------------------- | -| `protected_branch.create` | A proteção de branch foi habilitada em um branch. | -| `protected_branch.destroy` | A proteção de branch foi desabilitada em um branch. | -| `protected_branch.dismiss_stale_reviews` | Enforcement of dismissing stale pull requests was updated on a branch. | +| Ação | Descrição | +| ---------------------------------------- | --------------------------------------------------------------------- | +| `protected_branch.create` | A proteção de branch foi habilitada em um branch. | +| `protected_branch.destroy` | A proteção de branch foi desabilitada em um branch. | +| `protected_branch.dismiss_stale_reviews` | A execução de pull requests obsoletos foram atualizados em um branch. | {%- ifversion ghes %} | `protected_branch.dismissal_restricted_users_teams` | A exigência de restrição de usuários e/ou equipes que podem ignorar avaliações foi atualizada em um branch. {%- endif %} | `protected_branch.policy_override` | Um requisito de proteção de branch foi sobrescrito pelo administrador de um repositório. | `protected_branch.rejected_ref_update` | Uma tentativa de atualização de branch foi rejeitada. | `protected_branch.required_status_override` | O status exigido verifica se o requisito de proteção do branch foi substituído pelo administrador de um repositório. | `protected_branch.review_policy_and_required_status_override` | As revisões necessárias e os requisitos de proteção de status requeridos foram ignorados pelo administrador de um repositório. | `protected_branch.review_policy_override` | O requisito de proteção da branch de revisões necessário foi substituído pelo administrador de um repositório. | `protected_branch.update_admin_enforced` | A proteção do branch foi aplicada para os administradores do repositório. {%- ifversion ghes %} -| `protected_branch.update_allow_deletions_enforcement_level` | A exigência de permitir aos usuários com acesso de push para excluir branches correspondentes foi atualizada em um branch. | `protected_branch.update_allow_force_pushes_enforcement_level` | A exigência da permissão de push forçado para todos os usuários com acesso de push foi atualizada em um branch. | `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch. +| `protected_branch.update_allow_deletions_enforcement_level` | A exigência de permitir aos usuários com acesso de push para excluir branches correspondentes foi atualizada em um branch. | `protected_branch.update_allow_force_pushes_enforcement_level` | A exigência da permissão de push forçado para todos os usuários com acesso de push foi atualizada em um branch. | `protected_branch.update_linear_history_requirement_enforcement_level` | A aplicação da exigência do histórico do commit linear foi atualizada em um branch. {%- endif %} -| `protected_branch.update_pull_request_reviews_enforcement_level` | Enforcement of required pull request reviews was updated on a branch. Pode ser `0`(desativado), `1`(não administrador), `2`(todos). | `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review was updated on a branch. | `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch. | `protected_branch.update_required_status_checks_enforcement_level` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_signature_requirement_enforcement_level` | Enforcement of required commit signing was updated on a branch. | `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_name` | A branch name pattern was updated for a branch. +| `protected_branch.update_pull_request_reviews_enforcement_level` | A aplicação das revisões exigidas do pull request foi atualizada em um branch. Pode ser `0`(desativado), `1`(não administrador), `2`(todos). | `protected_branch.update_require_code_owner_review` | A aplicação da revisão exigida de um proprietário de código foi atualizada em um branch. | `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch. | `protected_branch.update_required_status_checks_enforcement_level` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_signature_requirement_enforcement_level` | Enforcement of required commit signing was updated on a branch. | `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_name` | A branch name pattern was updated for a branch. ### ações de categoria `public_key` diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 9d9ec1d225..70824b9301 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -35,10 +35,10 @@ A conta corporativa em {% ifversion ghes %}{% data variables.product.product_loc As organizações são contas compartilhadas em que os integrantes da empresa podem colaborar em muitos projetos de uma só vez. Os proprietários da organização podem gerenciar o acesso aos dados e projetos da organização, com recursos sofisticados de segurança e administrativos. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". {% ifversion ghec %} -Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +Os proprietários da empresa podem convidar organizações existentes para participar da conta corporativa ou criar novas organizações nas configurações da empresa. {% endif %} -Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." +Sua conta corporativa permite que você gerencie e aplique as políticas para todas as organizações pertencentes à empresa. {% data reusables.enterprise.about-policies %} Para obter mais informações, consulte "[Sobre as políticas corporativas](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)". {% ifversion ghec %} diff --git a/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md b/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md index 7745c104c2..f630153870 100644 --- a/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md +++ b/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md @@ -16,7 +16,7 @@ shortTitle: Criar conta corporativa {% data variables.product.prodname_ghe_cloud %} inclui a opção de criar uma conta corporativa, que permite a colaboração entre várias organizações e fornece aos administradores um único ponto de visibilidade e gestão. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". -{% data reusables.enterprise.create-an-enterprise-account %} Se você pagar por fatura, você poderá criar uma conta corporativa em {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you. +{% data reusables.enterprise.create-an-enterprise-account %} Se você pagar por fatura, você poderá criar uma conta corporativa em {% data variables.product.prodname_dotcom %}. Caso contrário, você pode [entrar em contato com nossa equipe de vendas](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) para criar uma conta corporativa para você. Uma conta corporativa está incluída em {% data variables.product.prodname_ghe_cloud %}. Portanto, a criação de uma não afetará a sua conta. @@ -29,9 +29,9 @@ Se a organização estiver conectada a {% data variables.product.prodname_ghe_se ## Criando uma conta corporativa em {% data variables.product.prodname_dotcom %} -To create an enterprise account, your organization must be using {% data variables.product.prodname_ghe_cloud %}. +Para criar uma conta corporativa, sua organização deve usar {% data variables.product.prodname_ghe_cloud %}. -If you pay by invoice, you can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. If you do not currently pay by invoice, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you. +Se você pagar por fatura, você pode criar uma conta corporativa diretamente por meio de {% data variables.product.prodname_dotcom %}. Se você atualmente não paga por fatura, você pode [entrar em contato com nossa equipe de vendas](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) para criar uma conta corporativa para você. {% data reusables.organizations.billing-settings %} diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md index 19bbbcdaf6..e39853e1dc 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md @@ -1,6 +1,6 @@ --- -title: About enterprise policies -intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.' +title: Sobre políticas corporativas +intro: 'Com as políticas corporativas, você pode gerenciar as políticas para todas as organizações pertencentes à sua empresa.' versions: ghec: '*' ghes: '*' @@ -11,18 +11,18 @@ topics: - Policies --- -To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. +Para ajudar você a aplicar as regras de negócios e a conformidade regulatória, as políticas fornecem um único ponto de gestão para todas as organizações pertencentes a uma conta corporativa. {% data reusables.enterprise.about-policies %} -For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise. +Por exemplo, com a política de "Permissões básicas", você pode permitir que os proprietários da organização configurem a política de "Permissões básicas" para sua organização, ou você pode exigir um nível específico de permissões de base, como "Leitura" para todas as organizações dentro da empresa. -By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." +Por padrão, nenhuma política corporativa é aplicada. Para identificar as políticas que devem ser aplicadas para atender aos requisitos únicos do seu negócio, Recomendamos analisar todas as políticas disponíveis na conta corporativa, começando com as políticas de gerenciamento do repositório. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)". -While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise. +Enquanto estiver configurando políticas coroprativas, para ajudar você a entender o impacto de alterar cada política, você pode ver as configurações atuais das organizações pertencentes à sua empresa. {% ifversion ghes %} -Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)." +Outra maneira de aplicar as normas na sua empresa é usar hooks pre-receive, que são scripts executados em {% data variables.product.product_location %} para implementar verificações de qualidade. Para obter mais informações, consulte "[Forçando política com hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks)". {% endif %} ## Leia mais diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index a23c8aecf0..25a15a3956 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -68,13 +68,13 @@ Você pode ver mais informações sobre o acesso da pessoa à sua empresa como, {% ifversion ghec %} ## Visualizando convites pendentes -You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. É possível filtrar a lista de forma útil, por exemplo, por organização. Ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome de exibição dela. +É possível ver todos os convites pendentes para se tornarem integrantes, administradores ou colaboradores externos na sua empresa. É possível filtrar a lista de forma útil, por exemplo, por organização. Ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome de exibição dela. -In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. +Na lista de integrantes pendentes, para qualquer conta individual, você pode cancelar todos os convites para participar de organizações pertencentes à sua empresa. Isto não cancela nenhum convite para que essa mesma pessoa se torne administrador corporativo ou colaborador externo. {% note %} -**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}. +**Observação:** Se um convite foi fornecido via SCIM, você deve cancelar o convite pelo seu provedor de identidade (IdP) em vez de {% data variables.product.prodname_dotcom %}. {% endnote %} @@ -85,7 +85,7 @@ Se você usar {% data variables.product.prodname_vss_ghe %}, a lista de convites 1. Em "Pessoas", clique em **Convites pendentes.**. ![Captura de tela da aba "Convites pendentes" na barra lateral](/assets/images/help/enterprises/pending-invitations-tab.png) -1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**. +1. Opcionalmente, para cancelar todos os convites de uma conta para participar de organizações pertencentes à sua empresa, à direita da conta, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e depois clique em **Cancelar convite**. ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png) 1. Opcionalmente, para visualizar os convites pendentes para administradores corporativos ou colaboradores externos, em "Integrantes pendentes", clique em **Administradores** ou **Colaboradores externos**. diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 017e46a867..7cb53834cd 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -50,7 +50,7 @@ Você pode efetuar a autenticação no {% data variables.product.product_name %} - Você criará uma senha ao criar sua conta em {% data variables.product.product_name %}. Recomendamos que você use um gerenciador de senhas para gerar uma senha aleatória e única. Para obter mais informações, consulte "[Criando uma senha forte](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - Se você não tiver habilitado a 2FA, {% data variables.product.product_name %} irá pedir verificação adicional quando você efetuar o login a partir de um dispositivo não reconhecido, como um novo perfil de navegador, um navegador onde os cookies foram excluídos ou um novo computador. - Depois de fornecer seu nome de usuário e senha, será solicitado que você forneça um código de verificação que enviaremos para você por e-mail. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} + Depois de fornecer seu nome de usuário e senha, será solicitado que você forneça um código de verificação que enviaremos para você por e-mail. Se você tiver o aplicativo de {% data variables.product.prodname_mobile %} instalado, você receberá uma notificação lá. Para obter mais informações, consulte "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)".{% endif %} - **Autenticação de dois fatores (2FA)** (recomendado) - Se você habilitar o 2FA, depois que você digitar seu nome de usuário e senha com sucesso, também vamos solicitar que você forneça um código gerado por um aplicativo {% ifversion fpt or ghec %} baseado em senha única (TOTP) no seu dispositivo móvel ou enviado como mensagem de texto (SMS){% endif %}. Para obter mais informações, consulte "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". - Além de autenticação com um aplicativo TOTP{% ifversion fpt or ghec %} ou uma mensagem de texto{% endif %}, você pode opcionalmente adicionar um método alternativo de autenticação com {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} ou{% endif %} uma chave de segurança usando WebAuthn. Para obter mais informações, consulte {% ifversion fpt or ghec %}"[Configurando autenticação de dois fatores com {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" e {% endif %}"[Configurando autenticação de dois fatores usando uma chave de segurança](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key).{% ifversion ghes %} @@ -93,7 +93,7 @@ Você pode trabalhar com todos os repositórios no {% data variables.product.pro Se você fizer a autenticação com {% data variables.product.prodname_cli %}, você poderá efetuar a autenticação com um token de acesso pessoal ou por meio do navegador web. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login). -Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação com um token de acesso pessoal. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). +Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação com um token de acesso pessoal. {% data reusables.user-settings.password-authentication-deprecation %} Sempre que você usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você insira as suas credenciais para efetuar a autenticação com {% data variables.product.product_name %}, a menos que você faça o armazenamento em cache com um [auxiliar de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git). diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 7dc03a5e4f..d93e9c7f88 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -80,5 +80,5 @@ Em vez de inserir manualmente seu PAT para cada operação de HTTPS do Git, voc ## Leia mais -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +- "[Sobre autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Vencimento e revogação do Token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index cc16b9ea52..5b5ba4532f 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -105,10 +105,10 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev ### Ações da categoria `oauth_authorization` -| Ação | Descrição | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create` | Acionada quando você [concede acesso a um {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | -| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando você [concede acesso a um {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | +| `destroy` | Acionada quando você [revoga o acesso de {% data variables.product.prodname_oauth_app %} à sua conta](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} e quando [as autorizações são revogadas ou vencem](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt or ghec %} @@ -174,25 +174,25 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev {% ifversion fpt or ghec %} ### ações de categoria de `patrocinadores` -| Ação | Descrição | -| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `custom_amount_settings_change` | Acionada quando você habilita ou desabilita os valores personalizados ou quando altera os valores sugeridos (consulte "[Gerenciar as suas camadas de patrocínio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | -| `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | -| `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create` | Acionada quando você patrocina uma conta (consulte "[Patrocinar um contribuidor de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_payment_complete` | Acionada depois que você patrocinar uma conta e seu pagamento ser processado (consulte [Patrocinando um colaborador de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_preference_change` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | -| `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | -| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | -| `sponsored_developer_disable` | Acionada quando sua conta {% data variables.product.prodname_sponsors %} está desabilitado | -| `sponsored_developer_redraft` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é retornada ao estado de rascunho a partir do estado aprovado | -| `sponsored_developer_profile_update` | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | -| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | -| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de uma camada de patrocínio (consulte "[Gerenciar suas camadas de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | -| `sponsored_developer_update_newsletter_send` | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | -| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | -| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| Ação | Descrição | +| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `custom_amount_settings_change` | Acionada quando você habilita ou desabilita os valores personalizados ou quando altera os valores sugeridos (consulte "[Gerenciar as suas camadas de patrocínio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create` | Acionada quando você patrocina uma conta (consulte "[Patrocinar um contribuidor de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_payment_complete` | Acionada depois que você patrocinar uma conta e seu pagamento ser processado (consulte [Patrocinando um colaborador de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve` | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (consulte "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_create` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_disable` | Acionada quando sua conta {% data variables.product.prodname_sponsors %} está desabilitado | +| `sponsored_developer_redraft` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é retornada ao estado de rascunho a partir do estado aprovado | +| `sponsored_developer_profile_update` | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Acionada quando você enviar seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de uma camada de patrocínio (consulte "[Gerenciar suas camadas de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | +| `sponsored_developer_update_newsletter_send` | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer` | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} a partir da lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `waitlist_join` | Acionada quando você se junta à lista de espera para tornar-se um desenvolvedor patrocinado (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | {% endif %} {% ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 5f0b328b4c..b13baab0af 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -57,7 +57,7 @@ Consulte "[Revisar integrações autorizadas](/articles/reviewing-your-authorize {% ifversion not ghae %} -If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. Para obter mais informações, consulte "[Revisar integrações autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". +Se você redefiniu sua senha da conta e gostaria de acionar um logout do aplicativo de {% data variables.product.prodname_mobile %}, você pode revogar a sua autorização do aplicativo OAuth "GitHub iOS" ou "GitHub Android". Isso encerrará todas as instâncias do aplicativo de {% data variables.product.prodname_mobile %} associado à sua conta. Para obter mais informações, consulte "[Revisar integrações autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". {% endif %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index 6bf90c1d20..830235940b 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -48,7 +48,7 @@ Os trabalhos que são executados em Windows e macOS runners que o {% data variab O armazenamento usado por um repositório é o armazenamento total usado por artefatos {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %}. Seu custo de armazenamento é o uso total de todos os repositórios de sua conta. Para obter mais informações sobre preços para {% data variables.product.prodname_registry %}, consulte "[Sobre cobrança para {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)." - If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} arredonda os minutos que cada trabalho usa até o minuto mais próximo. + Se o uso da sua conta ultrapassar esses limites e você definir um limite de gastos acima de US$ 0, você pagará US$ 0,008 por GB de armazenamento por dia e uso por minuto, dependendo do sistema operacional usado pelo executor hospedado em {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} arredonda os minutos que cada trabalho usa até o minuto mais próximo. {% note %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index 8e37eec43e..893b5f6d2c 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -50,9 +50,9 @@ Todos os dados transferidos, quando acionados por {% data variables.product.prod O uso do armazenamento é compartilhado com artefatos de construção produzidos por {% data variables.product.prodname_actions %} para repositórios de sua conta. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -O {% data variables.product.prodname_dotcom %} cobra o uso da conta que possui o repositório onde o pacote é publicado. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. +O {% data variables.product.prodname_dotcom %} cobra o uso da conta que possui o repositório onde o pacote é publicado. Se o uso da sua conta ultrapassar esses limites e você definir um limite de gastos acima de US$ 0, você pagará US$ 0,008 por GB de armazenamento por dia e US$ 0,50 por GB de transferência de dados. -Por exemplo, se sua organização usa {% data variables.product.prodname_team %}, permite gastos ilimitados, usa 150GB de armazenamento, e possui 50GB de transferência de dados durante um mês, a organização teria excessos de 148GB para armazenamento e 40GB para transferência de dados para esse mês. The storage overage would cost $0.008 USD per GB per day or $37 USD. O excesso para transferência de dados custaria US$ 0,50 ou US$ 20 por GB. +Por exemplo, se sua organização usa {% data variables.product.prodname_team %}, permite gastos ilimitados, usa 150GB de armazenamento, e possui 50GB de transferência de dados durante um mês, a organização teria excessos de 148GB para armazenamento e 40GB para transferência de dados para esse mês. O excesso de armazenamento custaria US$ 0,008 por GB por dia ou US$ 37. O excesso para transferência de dados custaria US$ 0,50 ou US$ 20 por GB. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index f0a81dfc60..e59abd8173 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -53,7 +53,7 @@ Cada usuário em {% data variables.product.product_location %} consome uma esta {% endif %} -{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +{% ifversion ghec %}Para clientes de {% data variables.product.prodname_ghe_cloud %} com uma conta corporativa, {% data variables.product.company_short %} contas por meio da sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. Para os clientes faturados, cada{% elsif ghes %}Para {% data variables.product.prodname_enterprise %} clientes faturados, {% data variables.product.company_short %} fatura por meio de uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. Cada{% endif %}atura inclui uma única cobrança de fatura para todos os seus serviços de {% data variables.product.prodname_dotcom_the_website %} pagos e as instâncias de qualquer instância de {% data variables.product.prodname_ghe_server %}. Para mais informações sobre {% ifversion ghes %} licenciamento, uso e faturas{% elsif ghec %}uso e faturas{% endif %}, consulte o seguinte{% ifversion ghes %} na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %} {%- ifversion ghes %} - "[Sobre preços por usuário](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)" diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 1b15944c6b..916efae146 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -17,7 +17,7 @@ shortTitle: Visualizar assinatura & uso ## Sobre a cobrança de contas corporativas -You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} +Você pode ver uma visão geral da{% ifversion ghec %}sua assinatura e uso licença paga{% elsif ghes %}{% endif %} para {% ifversion ghec %}sua{% elsif ghes %}a{% endif %} conta corporativa em {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, consulte[Criando uma conta corporativa](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} Para {% data variables.product.prodname_enterprise %} clientes faturados{% ifversion ghes %} que usam {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}{% endif %}, cada fatura inclui as informações sobre os serviços cobrados para todos os produtos. Por exemplo, além do seu uso para {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, você pode ter uso para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. Você também pode ter uso em {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licenças pagas em organizações fora da conta corporativa, pacotes de dados para {% data variables.large_files.product_name_long %}ou assinaturas de aplicativos em {% data variables.product.prodname_marketplace %}. Para obter mais informações sobre faturas, consulte "[Gerenciando faturas para a sua empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}. "{% elsif ghes %}" na documentação de {% data variables.product.prodname_dotcom_the_website %} .{% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 60ed88d52d..25fc46a9ec 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -147,7 +147,7 @@ Os nomes das verificações de análise de {% data variables.product.prodname_co ![Verificações de pull request de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) -Quando os trabalhos de {% data variables.product.prodname_code_scanning %} forem concluídos, {% data variables.product.prodname_dotcom %} calcula se quaisquer alertas foram adicionados pelo pull request e adiciona a entrada "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" à lista de verificações. Depois de {% data variables.product.prodname_code_scanning %} ser executado pelo menos uma vez, você poderá clicar em **Detalhes** para visualizar os resultados da análise. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +Quando os trabalhos de {% data variables.product.prodname_code_scanning %} forem concluídos, {% data variables.product.prodname_dotcom %} calcula se quaisquer alertas foram adicionados pelo pull request e adiciona a entrada "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" à lista de verificações. Depois de {% data variables.product.prodname_code_scanning %} ser executado pelo menos uma vez, você poderá clicar em **Detalhes** para visualizar os resultados da análise. Se você usou um pull request para adicionar {% data variables.product.prodname_code_scanning %} ao repositório, inicialmente você verá uma mensagem de {% ifversion fpt or ghes > 3.2 or ghae or ghec %} "Análise não encontrada"{% else %}"Análise ausente"{% endif %} ao clicar em **Detalhes** na verificação de "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME". {% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Análise não encontrada para mensagem de commit](/assets/images/help/repository/code-scanning-analysis-not-found.png) @@ -165,7 +165,7 @@ Por exemplo, na captura de tela acima, {% data variables.product.prodname_code_s ### Motivos para a mensagem "Análise ausente" {% endif %} -Depois que {% data variables.product.prodname_code_scanning %} analisou o código em um pull request, ele precisa comparar a análise do branch de tópico (o branch que você usou para criar o pull request) com a análise do branch de base (o branch no qual você deseja mesclar o pull request). Isso permite que {% data variables.product.prodname_code_scanning %} calcule quais alertas foram recém-introduzidos pelo pull request, que alertas já estavam presentes no branch de base e se alguns alertas existentes são corrigidos pelas alterações no pull request. Inicialmente, se você usar um pull request para adicionar {% data variables.product.prodname_code_scanning %} a um repositório, o branch de base ainda não foi analisado. Portanto, não é possível computar esses detalhes. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. +Depois que {% data variables.product.prodname_code_scanning %} analisou o código em um pull request, ele precisa comparar a análise do branch de tópico (o branch que você usou para criar o pull request) com a análise do branch de base (o branch no qual você deseja mesclar o pull request). Isso permite que {% data variables.product.prodname_code_scanning %} calcule quais alertas foram recém-introduzidos pelo pull request, que alertas já estavam presentes no branch de base e se alguns alertas existentes são corrigidos pelas alterações no pull request. Inicialmente, se você usar um pull request para adicionar {% data variables.product.prodname_code_scanning %} a um repositório, o branch de base ainda não foi analisado. Portanto, não é possível computar esses detalhes. Neste caso, quando você clicar nos resultados verificando o pull request você verá a mensagem {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Análise não encontrada"{% else %}"Análise ausente do commit base SHA-HASH"{% endif %}. Há outras situações em que não pode haver análise para o último commit do branch de base para um pull request. Isso inclui: diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 9fbe7b008a..77f7485a4d 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -42,7 +42,7 @@ Há muitas opções para configurar {% data variables.product.prodname_code_scan Para todas as configurações de {% data variables.product.prodname_code_scanning %}, a verificação que contém os resultados de {% data variables.product.prodname_code_scanning %} é: **resultados de {% data variables.product.prodname_code_scanning_capc %}**. Os resultados de cada ferramenta de análise utilizada são mostrados separadamente. Todos os novos alertas gerados por alterações no pull request são exibidos como anotações. -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. Isso abre a visualização completa de alerta onde você pode filtrar todos os alertas sobre o branch por tipo, gravidade, tag, etc. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts). " +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Para ver o conjunto completo de alertas para o branch analisado, clique em **Ver todos os alertas do branch**. Isso abre a visualização completa de alerta onde você pode filtrar todos os alertas sobre o branch por tipo, gravidade, tag, etc. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts). " ![Verificação de resultados de {% data variables.product.prodname_code_scanning_capc %} em um pull request](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index eb2b34ac23..64d175fd66 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -63,7 +63,7 @@ Se as atualizações de segurança não estiverem habilitadas para o seu reposit Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para um repositório individual (veja abaixo). -Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios pertencentes à sua conta pessoal ou organização. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios pertencentes à sua conta pessoal ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta pessoal](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". O {% data variables.product.prodname_dependabot_security_updates %} exige configurações específicas do repositório. Para obter mais informações, consulte "[Repositórios compatíveis](#supported-repositories)". diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index c22896468c..5a177807e3 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Atualizações de versão do Dependabot O {% data variables.product.prodname_dependabot %} facilita a manutenção de suas dependências. Você pode usá-lo para garantir que seu repositório se mantenha atualizado automaticamente com as versões mais recentes dos pacotes e aplicações do qual ele depende. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. +Você habilita {% data variables.product.prodname_dependabot_version_updates %} verificando um arquivo de configuração do `dependabot.yml` no seu repositório. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md index e12a57947b..2b55a3c33f 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md @@ -138,7 +138,7 @@ Você pode visualizar e gerenciar alertas de funcionalidades de segurança para {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". {% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}Você{% elsif fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% endif %} podem visualizar, filtrar e ordenar alertas de seguranla para repositórios pertencentes à {% ifversion ghes > 3.1 or ghec or ghae %}sua{% elsif fpt %}their{% endif %} organização na visão geral de segurança. Para obter mais informações, consulte{% ifversion ghes or ghec or ghae %} "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview).{% elsif fpt %} "[Sobre a visão geral de segurança](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" na documentação de {% data variables.product.prodname_ghe_cloud %} .{% endif %}{% endif %} {% ifversion ghec %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md index 7c4fe8cbae..06cd551675 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md @@ -75,7 +75,7 @@ Para obter mais informações, consulte "[Explorar as dependências de um reposi {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}." +Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" e "[Gerenciando configurações de segurança e análise da sua conta pessoal](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}". {% endif %} diff --git a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 380b010919..a4eacfd050 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -15,7 +15,7 @@ topics: - Secret scanning --- -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **Observação:** Os padrões personalizados para {% data variables.product.prodname_secret_scanning %} estão atualmente em fase beta e sujeitos a alterações. @@ -33,7 +33,7 @@ Você pode definir padrões personalizados para identificar segredos que não s {%- else %} 20 padrões personalizados para cada organização ou conta corporativa, e por repositório. {%- endif %} -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.3 %} {% note %} **Observação:** No beta, existem algumas limitações ao usar padrões personalizados para {% data variables.product.prodname_secret_scanning %}: diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md index 3a58cd7b19..23ff10535a 100644 --- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md @@ -69,7 +69,7 @@ A nível da organização, a visão geral de segurança exibe informações de s {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### Sobre a visão geral de segurança do nível da empresa -A nível da empresa, a visão geral de segurança exibe informações de segurança agregadas e específicas ao repositório para sua empresa. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise. +A nível da empresa, a visão geral de segurança exibe informações de segurança agregadas e específicas ao repositório para sua empresa. É possível visualizar repositórios pertencentes à sua empresa que tenham alertas de segurança, visualizar todos os alertas de segurança ou alertas específicos de segurança de toda a empresa. Os proprietários da organização e os gerentes de segurança das organizações da sua empresa também têm acesso limitado à visão geral de segurança no nível da empresa. Eles só podem ver repositórios e alertas das organizações aos quais têm acesso total. diff --git a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md index be16d4e818..6e9abb858f 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md @@ -19,7 +19,7 @@ topics: Basicamente, a segurança de abastecimento de software de ponta a ponta consiste em garantir que o código que você distribui não tenha sido adulterado. Anteriormente, os invasores focaram em direcionar as dependências que você usa, por exemplo, bibliotecas e estruturas. Os invasores agora expandiram o seu foco para incluir as contas de usuários direcionadas e criar processos. Portanto, esses sistemas também devem ser defendidos. -For information about features in {% data variables.product.prodname_dotcom %} that can help you secure dependencies, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." +Para obter informações sobre funcionalidades em {% data variables.product.prodname_dotcom %} que podem ajudar você a proteger dependências, consulte "[Sobre a segurança da cadeia de suprimentos](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." ## Sobre estes guias diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 73e0f80c88..27ae40edaf 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -37,7 +37,7 @@ Para obter mais informações sobre como configurar uma revisão de dependência A revisão de dependências é compatível com as mesmas linguagens e os mesmos ecossistemas de gestão de pacotes do gráfico de dependência. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". -For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." +Para obter mais informações sobre as funcionalidades da cadeia de suprimentos disponíveis em {% data variables.product.product_name %}, consulte "[Sobre a segurança da cadeia de suprimentos](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." {% ifversion ghec or ghes %} ## Habilitar revisão de dependências diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 3b692d1fa2..948f1762f8 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -55,7 +55,7 @@ Os dados de dependência de referência cruzada de {% data variables.product.pro {% endif %} {% ifversion fpt or ghec or ghes %} -For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)." +Para oter guias sobre as práticas recomendadas de segurança da cadeia de suprimentos de ponta a ponta, incluindo a proteção de contas pessoais, código e processos de compilação, consulte "[Protegendo sua cadeia de suprimentos de ponta a ponta](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)". {% endif %} ## Visão geral de recursos @@ -132,7 +132,7 @@ Para obter mais informações sobre {% data variables.product.prodname_dependabo Repositórios públicos: - **Gráfico de dependência**—habilitado por padrão e não pode ser desabilitado. - **Revisão de dependência**—habilitado por padrão e não pode ser desabilitado. -- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. {% data variables.product.prodname_dotcom %} detecta dependências vulneráveis e exibe informações no gráfico de dependência, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários do repositório ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %}. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." +- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. {% data variables.product.prodname_dotcom %} detecta dependências vulneráveis e exibe informações no gráfico de dependência, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários do repositório ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %}. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciando as configurações de segurança e análise da sua conta de usuário](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" ou "[Gerenciando as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". Repositórios privados: - **Gráfico de dependência**—não habilitado por padrão. O recurso pode ser habilitado pelos administradores do repositório. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". @@ -141,7 +141,7 @@ Repositórios privados: {% elsif ghec %} - **Revisão de dependência**— disponível em repositórios privados pertencentes a organizações, desde que você tenha uma licença para {% data variables.product.prodname_GH_advanced_security %} e o gráfico de dependências habilitado. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" e "[Explorando as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". {% endif %} -- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." +- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciando as configurações de segurança e análise da sua conta de usuário](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" ou "[Gerenciando as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". Qualquer tipo de repositório: - **{% data variables.product.prodname_dependabot_security_updates %}**—não habilitado por padrão. É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 55c2f326f8..0729fdc08b 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -45,7 +45,7 @@ O gráfico de dependências inclui todas as dependências de um repositório det O gráfico de dependências identifica as dependências indiretas{% ifversion fpt or ghec %} explicitamente a partir de um arquivo de bloqueio ou verificando as dependências das suas dependências diretas. Para o gráfico mais confiável, você deve usar os arquivos de bloqueio (ou o equivalente deles), pois definem exatamente quais versões das dependências diretas e indiretas você usa atualmente. Se você usar arquivos de bloqueio, você também terá certeza de que todos os contribuidores do repositório usarão as mesmas versões, o que facilitará para você testar e depurar o código{% else %} dos arquivos de bloqueio{% endif %}. -For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." +Para obter mais informações sobre como {% data variables.product.product_name %} ajuda você a entender as dependências do seu ambiente, consulte "[Sobre a segurança da cadeia de suprimentos](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." {% ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md index ec256a7367..300456dbeb 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md @@ -42,7 +42,7 @@ Embora esta opção não configure um ambiente de desenvolvimento para você, el ## Opção 4: Usar contêineres remotos e o Docker para um ambiente contêinerizado local -If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. O tempo de configuração desta opção irá variar dependendo das suas especificações locais e da complexidade da configuração do seu contêiner de desenvolvimento. +Se o seu repositório tiver um `devcontainer.json`, considere o uso da [extensão Remote-Containers](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) em {% data variables.product.prodname_vscode %} para construir e anexar a um contêiner de desenvolvimento local para o seu repositório. O tempo de configuração desta opção irá variar dependendo das suas especificações locais e da complexidade da configuração do seu contêiner de desenvolvimento. {% note %} diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md index f783922601..ad4058d2ab 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md @@ -34,7 +34,7 @@ Cada codespace tem a sua própria rede virtual isolada. Usamos firewalls para bl ### Autenticação -You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. +Você pode se conectar a um codespace usando um navegador da web ou a partir de {% data variables.product.prodname_vscode %}. Se você se conectar a partir de {% data variables.product.prodname_vscode_shortname %}, será solicitado que você efetue a autenticação com {% data variables.product.product_name %}. Toda vez que um codespace é criado ou reiniciado, atribui-se um novo token de {% data variables.product.company_short %} com um período de vencimento automático. Este período permite que você trabalhe no código sem precisar efetuar a autenticação novamente durante um dia de trabalho típico, mas reduz a chance de deixar uma conexão aberta quando você parar de usar o codespace. diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md index a88957477f..fceae23801 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md @@ -17,7 +17,7 @@ redirect_from: ## Usar {% data variables.product.prodname_copilot %} -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), um programador de par de IA pode ser usado em qualquer codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), um programador de par de IA pode ser usado em qualquer codespace. Para começar a usar {% data variables.product.prodname_copilot_short %} em {% data variables.product.prodname_codespaces %}, instale a extensão de [{% data variables.product.prodname_copilot_short %} a partir de {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). Para incluir o {% data variables.product.prodname_copilot_short %}, ou outras extensões, em todos os seus codespaces, habilite a sincronização de Configurações. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". Além disso, para incluir {% data variables.product.prodname_copilot_short %} em um determinado projeto para todos os usuários, você pode especificar `GitHub.copilot` como uma extensão no seu arquivo `devcontainer.json`. Para obter informações sobre a configuração de um arquivo `devcontainer.json`, consulte "[Introdução aos contêineres de desenvolvimento](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)". diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 07886721b7..f3e98c1981 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -35,7 +35,7 @@ Para obter mais informações sobre o que acontece quando você cria um codespac Para obter mais informações sobre o ciclo de vida de um codespace, consulte "[Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)". -Se você quiser usar hooks do Git para o seu código, você deverá configurar hooks usando os scritps do ciclo de vida do de [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), como `postCreateCommand`, durante a etapa 4. Uma vez que o seu contêiner de codespace é criado depois que o repositório é clonado, qualquer [diretório de template do git](https://git-scm.com/docs/git-init#_template_directory) configurado na imagem do contêiner não será aplicado ao seu codespace. Os Hooks devem ser instalados depois que o codespace for criado. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. +Se você quiser usar hooks do Git para o seu código, você deverá configurar hooks usando os scritps do ciclo de vida do de [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), como `postCreateCommand`, durante a etapa 4. Uma vez que o seu contêiner de codespace é criado depois que o repositório é clonado, qualquer [diretório de template do git](https://git-scm.com/docs/git-init#_template_directory) configurado na imagem do contêiner não será aplicado ao seu codespace. Os Hooks devem ser instalados depois que o codespace for criado. Para obter mais informações sobre como usar `postCreateCommand`, consulte a referência do [`devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) na documentação de {% data variables.product.prodname_vscode_shortname %}. {% data reusables.codespaces.use-visual-studio-features %} diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index 470dc14044..fbb0248b3e 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -30,7 +30,7 @@ Se você preferir trabalhar no navegador, mas deseja continuar usando suas exten Para desenvolver-se em uma plataforma de codespace diretamente em {% data variables.product.prodname_vscode_shortname %}, você deverá instalar e efetuar o login na extensão {% data variables.product.prodname_github_codespaces %} com as suas credenciais de {% data variables.product.product_name %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode_shortname %}. -Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode_shortname %}. +Use o {% data variables.product.prodname_vscode_marketplace %} para instalar a extensão [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode_shortname %}. {% mac %} @@ -106,7 +106,7 @@ Use the {% data variables.product.prodname_vscode_marketplace %} to install the ## Alternando para a compilação de Insiders de {% data variables.product.prodname_vscode_shortname %} -You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. +Você pode usar o [Compilação de Insiders de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) dentro de {% data variables.product.prodname_codespaces %}. 1. Na parte inferior esquerda da sua janela {% data variables.product.prodname_codespaces %}, selecione **Configurações de {% octicon "gear" aria-label="The settings icon" %}**. 2. Na lista, selecione "Alternar para Versão de Insiders". diff --git a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md index 49fab2e9af..42f6859d45 100644 --- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md +++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md @@ -46,13 +46,13 @@ Uma vez que seu repositório é clonado na VM de host antes da criação do cont ### Etapa 3: Conectando-se ao codespace -Quando seu contêiner for criado e qualquer outra inicialização for executada, você estará conectado ao seu codespace. You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. +Quando seu contêiner for criado e qualquer outra inicialização for executada, você estará conectado ao seu codespace. Você pode conectar-se por meio da web ou via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), ou ambos, se necessário. ### Passo 4: Configuração de pós-criação Uma vez que você estiver conectado ao seu codespace, a sua configuração automatizada poderá continuar compilando com base na configuração que você especificou no seu arquivo `devcontainer.json`. Você pode ver `postCreateCommand` e `postAttachCommand` serem executados. -Se vocÊ quiser usar os hooks do Git no seu codespace, configure os hooks usando os scripts do ciclo de vida do [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) como, por exemplo, `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. +Se vocÊ quiser usar os hooks do Git no seu codespace, configure os hooks usando os scripts do ciclo de vida do [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) como, por exemplo, `postCreateCommand`. Para obter mais informações, consulte a referência de [`devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) na documentação de {% data variables.product.prodname_vscode_shortname %}. Se você tiver um repositório de dotfiles público para {% data variables.product.prodname_codespaces %}, você poderá habilitá-lo para uso com novos codespaces. Quando habilitado, seus dotfiles serão clonados para o contêiner e o script de instalação será invocado. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)". @@ -93,7 +93,7 @@ A execução do seu aplicativo ao chegar pela primeira vez no seu codespace pode ## Enviando e fazendo push das suas alterações -O Git está disponível por padrão no seu codespace. Portanto, você pode confiar no fluxo de trabalho do Git existente. You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +O Git está disponível por padrão no seu codespace. Portanto, você pode confiar no fluxo de trabalho do Git existente. Você pode trabalhar com o Git no seu codespace por meio do Terminal ou usando [a interface de usuário do controle de origem de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol). Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" ![Executando o status do git no terminal do codespaces](/assets/images/help/codespaces/git-status.png) @@ -107,7 +107,7 @@ Você pode criar um codespace a partir de qualquer branch, commit ou pull reques ## Personalizando seu codespace com extensões -Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. Para obter informações de como as extensões são executadas em {% data variables.product.prodname_codespaces %}, consulte [Suporte ao Desenvolvimento Remoto e aos codespaces do GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) na documentação de {% data variables.product.prodname_vscode_shortname %}. +Usar {% data variables.product.prodname_vscode_shortname %} no seu codespace dá acesso aos {% data variables.product.prodname_vscode_marketplace %} para que você possa adicionar as extensões que precisar. Para obter informações de como as extensões são executadas em {% data variables.product.prodname_codespaces %}, consulte [Suporte ao Desenvolvimento Remoto e aos codespaces do GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) na documentação de {% data variables.product.prodname_vscode_shortname %}. Se você já usa o {% data variables.product.prodname_vscode_shortname %}, você pode usar as [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automaticamente as extensões, configurações, temas, e atalhos de teclado entre sua instância local e todos {% data variables.product.prodname_codespaces %} que você criar. diff --git a/translations/pt-BR/content/codespaces/getting-started/quickstart.md b/translations/pt-BR/content/codespaces/getting-started/quickstart.md index e439816d58..b06b799ded 100644 --- a/translations/pt-BR/content/codespaces/getting-started/quickstart.md +++ b/translations/pt-BR/content/codespaces/getting-started/quickstart.md @@ -72,7 +72,7 @@ Agora que você fez algumas alterações, você poderá usar o terminal integrad ## Personalizando com uma extensão -Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. Para este exemplo, você instalará uma extensão que altera o tema, mas você pode instalar qualquer extensão que seja útil para o seu fluxo de trabalho. +Dentro de um codespace, você tem acesso ao {% data variables.product.prodname_vscode_marketplace %}. Para este exemplo, você instalará uma extensão que altera o tema, mas você pode instalar qualquer extensão que seja útil para o seu fluxo de trabalho. 1. Na barra lateral esquerda, clique no ícone Extensões. @@ -84,7 +84,7 @@ Within a codespace, you have access to the {% data variables.product.prodname_vs ![Selecionar tema fairyfloss](/assets/images/help/codespaces/fairyfloss.png) -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account. +4. As alterações feitas na configuração do seu ditor editor no codespace atual, como ligações de tema e teclado, são sincronizadas automaticamente por meio da [Sincronização das Configurações](https://code.visualstudio.com/docs/editor/settings-sync) para qualquer outro codespace que você abrir e quaisquer instâncias do {% data variables.product.prodname_vscode %} que estiverem conectadas à sua conta do GitHub. ## Próximos passos diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md index f18687ac03..dbbb7a10dd 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md @@ -41,7 +41,7 @@ Você também pode limitar os usuários individuais que podem usar {% data varia ## Excluindo codespaces não utilizados -Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}. +Seus usuários podem excluir seus codespaces em https://github.com/codespaces e de dentro de {% data variables.product.prodname_vscode %}. Para reduzir o tamanho de um codespace, os usuários podem excluir arquivos manualmente usando o terminal ou de dentro de {% data variables.product.prodname_vscode_shortname %}. {% note %} diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index ecdbcbd3fa..42df5fe81b 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -25,7 +25,7 @@ Quando as permissões são listadas no arquivo `devcontainer.json`, será solici Para criar codespaces com permissões personalizadas definidas, você deve usar um dos seguintes: * A interface de usuário web do {% data variables.product.prodname_dotcom %} * [CLI de {% data variables.product.prodname_dotcom %}](https://github.com/cli/cli/releases/latest) 2.5.2 ou posterior -* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later +* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extensão ](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 ou posterior ## Configurando permissões adicionais do repositório diff --git a/translations/pt-BR/content/codespaces/overview.md b/translations/pt-BR/content/codespaces/overview.md index 6866957425..939a97b6cb 100644 --- a/translations/pt-BR/content/codespaces/overview.md +++ b/translations/pt-BR/content/codespaces/overview.md @@ -34,7 +34,7 @@ Para personalizar os tempos de execução e ferramentas no seu codespace, é pos Se você não adicionar uma configuração de contêiner de desenvolvimento, o {% data variables.product.prodname_codespaces %} clonará seu repositório em um ambiente com a imagem de código padrão que inclui muitas ferramentas, linguagens e ambientes de tempo de execução. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". -Você também pode personalizar aspectos do ambiente do seu codespace usando um repositório público do [dotfiles](https://dotfiles.github.io/tutorials/) e [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. Para obter mais informações, consulte[Personalizando seu codespace](/codespaces/customizing-your-codespace)". +Você também pode personalizar aspectos do ambiente do seu codespace usando um repositório público do [dotfiles](https://dotfiles.github.io/tutorials/) e [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync). A personalização pode incluir preferências do shell, ferramentas adicionais, configurações do editor e extensões de {% data variables.product.prodname_vscode_shortname %}. Para obter mais informações, consulte[Personalizando seu codespace](/codespaces/customizing-your-codespace)". ## Sobre a cobrança do {% data variables.product.prodname_codespaces %} diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index ce3629c19d..3012f43691 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -110,7 +110,7 @@ Para usar um arquivo Dockerfile como parte de uma configuração de contêiner d } ``` -For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." +Para obter mais informações sobre como usar um arquivo Docker em uma configuração de contêiner de desenvolvimento, consulte a documentação de {% data variables.product.prodname_vscode_shortname %} "[Criar um contêiner de desenvolvimento](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile). " ## Usando a configuração padrão do contêiner de desenvolvimento @@ -122,7 +122,7 @@ A configuração padrão é uma boa opção se você estiver trabalhando em um p ## Usando uma configuração de contêiner predefinida -É possível escolher uma lista de configurações predefinidas para criar uma configuração de contêiner de desenvolvimento para o seu repositório. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. +É possível escolher uma lista de configurações predefinidas para criar uma configuração de contêiner de desenvolvimento para o seu repositório. Essas configurações fornecem configurações comuns para determinados tipos de projeto e podem ajudar você rapidamente a começar com uma configuração que já tem as opções de contêiner apropriadas, configurações do {% data variables.product.prodname_vscode_shortname %} e extensões do {% data variables.product.prodname_vscode_shortname %} que devem ser instaladas. Usar uma configuração predefinida é uma ótima ideia se você precisa de uma extensão adicional. Você também pode começar com uma configuração predefinida e alterá-la conforme necessário para o seu projeto. @@ -172,51 +172,51 @@ Você pode adicionar algumas das características mais comuns selecionando-as na Se nenhuma das configurações predefinidas atender às suas necessidades, você poderá criar uma configuração personalizada escrevendo seu próprio arquivo `devcontainer.json`. * Se você estiver adicionando um único arquivo `devcontainer.json` que será usado por todos que criarem um código a partir do seu repositório, crie o arquivo dentro de um diretório `.devcontainer` na raiz do repositório. -* If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory. +* Se quiser oferecer aos usuários uma escolha de configuração, você poderá criar vários arquivos de `devcontainer.json`, cada um localizado em um subdiretório separado do diretório `.devcontainer`. {% note %} - **Note**: You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not. + **Observação**: Você não pode encontrar os seus arquivos `devcontainer.json` arquivos em diretórios mais de um nível abaixo de `.devcontainer`. Por exemplo, um arquivo em `.devcontainer/teamA/devcontainer.json` irá funcionar, mas `.devcontainer/teamA/testing/devcontainer.json` não irá funcionar. {% endnote %} - If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". + Se vários arquivos `devcontainer.json` forem encontrados no repositório, eles serão listados na página de opções de criação do codespace. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". - ![A choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png) + ![Uma escolha de arquivos de configuração](/assets/images/help/codespaces/configuration-file-choice.png) -### Default configuration selection during codespace creation +### Seleção de configuração padrão durante a criação de codespace -If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. Se nenhum dos dois arquivos existir, a configuração padrão do contêiner de desenvolvimento será selecionada por padrão. +If `.devcontainer/devcontainer.json` ou `.devcontainer.json` existir, será a seleção padrão na lista de arquivos de configuração disponíveis quando você criar um codespace. Se nenhum dos dois arquivos existir, a configuração padrão do contêiner de desenvolvimento será selecionada por padrão. ![A configuração padrão selecionada](/assets/images/help/codespaces/configuration-file-choice-default.png) ### Editando o arquivo devcontainer.json -You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} +Você pode adicionar e editar as chaves de configuração compatíveis no arquivo `devcontainer.json` para especificar aspectos do ambiente do codespace como, por exemplo, quais extensões de {% data variables.product.prodname_vscode_shortname %} serão instaladas. {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC format. Isso permite que você inclua comentários no arquivo de configuração. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +O arquivo `devcontainer.json` é gravado usando o formato JSONC. Isso permite que você inclua comentários no arquivo de configuração. Para obter mais informações, consulte "[Editando o JSON com {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" na documentação do {% data variables.product.prodname_vscode_shortname %}. {% note %} -**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors. +**Observaçãp**: Se você usar um linter para validar o arquivo `devcontainer.json`, certifique-se que está definido como JSONC e não JSON ou comentários serão relatados como erros. {% endnote %} -### Editor settings for {% data variables.product.prodname_vscode_shortname %} +### Configurações do editor para {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.vscode-settings-order %} -You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. +Você pode definir configurações de editor padrão para {% data variables.product.prodname_vscode_shortname %} em dois lugares. -* Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. -* Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. +* As configurações do editor definidas no arquivo `.vscode/settings.json` no repositório são aplicadas como configurações com escopo dafinido no _Espaço de trabalho_ no codespace. +* As configurações do editor definidas nas chave `configurações` no arquivo `devcontainer.json` são aplicadas como configurações com escopo definido como _Remote [Codespaces]configurações de escopo_ no codespace. -## Applying configuration changes to a codespace +## Aplicando alterações de configuração a um codespace {% data reusables.codespaces.apply-devcontainer-changes %} {% data reusables.codespaces.rebuild-command %} -1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. +1. {% data reusables.codespaces.recovery-mode %} Corrija os erros na configuração. ![Mensagem de erro sobre modo de recuperação](/assets/images/help/codespaces/recovery-mode-error-message.png) diff --git a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md index 8cc2dad801..40f51f353a 100644 --- a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md @@ -49,7 +49,7 @@ Tanto o {% data variables.product.prodname_serverless %} quanto o {% data variab | **Inicialização** | O {% data variables.product.prodname_serverless %} abre instantaneamente com um toque de tecla e você pode começar a usá-lo imediatamente, sem ter que esperar por uma configuração ou instalação adicional. | Ao criar ou retomar um codespace, o código é atribuído a uma VM e o contêiner é configurado com base no conteúdo de um arquivo `devcontainer.json`. Essa configuração pode levar alguns minutos para criar o ambiente. Para obter mais informações, consulte "[Criando um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | | **Calcular** | Não há nenhum computador associado. Portanto você não conseguirá criar e executar o seu código ou usar o terminal integrado. | Com {% data variables.product.prodname_codespaces %}, você obtém o poder da VM dedicada na qual você pode executar e depurar seu aplicativo. | | **Acesso ao terminal** | Nenhum. | {% data variables.product.prodname_codespaces %} fornece um conjunto comum de ferramentas por padrão, o que significa que você pode usar o Terminal exatamente como você faria no seu ambiente local. | -| **Extensões** | Apenas um subconjunto de extensões que podem ser executadas na web aparecerão na visualização de extensões e podem ser instaladas. Para obter mais informações, consulte "[Usando as extensões](#using-extensions)." | With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}. | +| **Extensões** | Apenas um subconjunto de extensões que podem ser executadas na web aparecerão na visualização de extensões e podem ser instaladas. Para obter mais informações, consulte "[Usando as extensões](#using-extensions)." | Com os codespaces, você pode usar a maioria das extensões do {% data variables.product.prodname_vscode_marketplace %}. | ### Continue trabalhando em {% data variables.product.prodname_codespaces %} diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 7034e18b8e..5a5b72f175 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -22,11 +22,11 @@ Ao criar um codespace, você pode escolher o tipo de máquina virtual que deseja ![Uma lista dos tipos de máquina disponíveis](/assets/images/help/codespaces/choose-custom-machine-type.png) -If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. +Se você tiver a sua preferência de editor de {% data variables.product.prodname_codespaces %} definida como "{% data variables.product.prodname_vscode %} para a Web", a página "Configurando seu codespace " mostrará a mensagem "Pré-compliação de codespace encontrada" se uma pré-compilação estiver sendo usada. ![A mensagem "codespaces da pre-criação encontrados"](/assets/images/help/codespaces/prebuilt-codespace-found.png) -Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. Para obter mais informações, consulte "[Definindo seu editor padrão para codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)". +Da mesma forma, se sua preferência de editor for "{% data variables.product.prodname_vscode_shortname %}", o terminal integrado conterá a mensagem "Você está em um codespace pré-criado e definido pela configuração de pré-compilação para seu repositório" ao criar um novo codespace. Para obter mais informações, consulte "[Definindo seu editor padrão para codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)". Depois de criar um codespace, você pode verificar se ele foi criado a partir de uma pré-compilação executando o seguinte comando {% data variables.product.prodname_cli %} no terminal: @@ -59,7 +59,7 @@ Essas são as coisas a serem verificadas se a etiqueta " Pré-compilação de {% ## Troubleshooting failed workflow runs for prebuilds -If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)." +Se o fluxo de trabalho for executado para uma configuração de pré-compilação falhar, você poderá desabilitar temporariamente a configuração de pré-compilação durante a investigação. Para obter mais informações, consulte "[Gereciando pré-compilações](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)". ## Leia mais diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index a37000fa48..f51a95eac9 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -239,8 +239,8 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Listar implementações](/rest/reference/deployments#list-deployments) * [Criar uma implementação](/rest/reference/deployments#create-a-deployment) -* [Get a deployment](/rest/reference/deployments#get-a-deployment) -* [Delete a deployment](/rest/reference/deployments#delete-a-deployment) +* [Obter uma implantação](/rest/reference/deployments#get-a-deployment) +* [Excluir uma implantação](/rest/reference/deployments#delete-a-deployment) #### Eventos @@ -573,7 +573,7 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de #### Reações -* [Delete a reaction](/rest/reference/reactions) +* [Excluir uma reação](/rest/reference/reactions) * [Listar reações para um comentário de commit](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [Criar reação para um comentário de commit](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [Listar reações para um problema](/rest/reference/reactions#list-reactions-for-an-issue) @@ -585,13 +585,13 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Listar reações para um comentário de discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [Criar reação para um comentário de discussão em equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [Listar reações para uma discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion) +* [Criar reação para uma discussão em equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [Excluir uma reação de comentário de commit](/rest/reference/reactions#delete-a-commit-comment-reaction) * [Excluir uma reação do problema](/rest/reference/reactions#delete-an-issue-reaction) * [Excluir uma reação a um comentário do commit](/rest/reference/reactions#delete-an-issue-comment-reaction) * [Excluir reação de comentário do pull request](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [Excluir reação para discussão em equipe](/rest/reference/reactions#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction) +* [Excluir reação para discussão em equipe](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### Repositórios diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md index fbd2ee7079..7e09e2ab30 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md @@ -85,7 +85,7 @@ Tenha em mente essas ideias ao usar os tokens de acesso pessoais: * Você pode realizar solicitações de cURL únicas. * Você pode executar scripts pessoais. * Não configure um script para toda a sua equipe ou empresa usá-lo. -* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} +* Não configure uma conta pessoal compartilhada para atuar como um usuário bot.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Defina um vencimento para os seus tokens de acesso pessoais para ajudar a manter suas informações seguras.{% endif %} ## Determinar qual integração criar diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 47a2cb6ec8..6307b18869 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1485,14 +1485,14 @@ Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no ### Objeto da carga do webhook -| Tecla | Tipo | Descrição | -| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------- | -| `inputs` | `objeto` | Inputs to the workflow. Each key represents the name of the input while it's value represents the value of that input. | +| Tecla | Tipo | Descrição | +| -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------- | +| `inputs` | `objeto` | Entradas para o fluxo de trabalho. Cada chave representa o nome do valor de entrada e o seu valor representa o valor dessa entrada. | {% data reusables.webhooks.org_desc %} -| `ref` | `string` | The branch ref from which the workflow was run. | +| `ref` | `string` | O ref do branch a partir do qual o fluxo de trabalho foi executado. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.sender_desc %} -| `workflow` | `string` | Relative path to the workflow file which contains the workflow. | +| `workflow` | `string` | Caminho relativo para o arquivo do fluxo de trabalho, que contém o fluxo de trabalho. | ### Exemplo de carga de webhook diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index 83437b27ce..3f87b8fe12 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,7 +1,7 @@ --- title: Sobre usar o Visual Studio Code com o GitHub Classroom shortTitle: Sobre o uso do Visual Studio Code -intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' +intro: 'Você pode configurar {% data variables.product.prodname_vscode %} como o editor preferido para as atividades em {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: @@ -10,30 +10,30 @@ redirect_from: ## Sobre o {% data variables.product.prodname_vscode %} -{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. Para obter mais informações sobre IDEs e {% data variables.product.prodname_classroom %}, consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +{% data variables.product.prodname_vscode %} é um editor de código fonte leve mas poderoso que é executado em seu computador e está disponível para Windows, macOS e Linux. Com a extensão do [GitHub Classroom para {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), os alunos podem facilmente navegar, editar, enviar, colaborar e testar suas atividades no Classroom. Para obter mais informações sobre IDEs e {% data variables.product.prodname_classroom %}, consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". ### Editor da escolha do seu aluno -The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains: +A integração do GitHub Classroom com {% data variables.product.prodname_vscode_shortname %} oferece aos alunos um pacote de extensão que contém: 1. [Extensão GitHub Classroom](https://aka.ms/classroom-vscode-ext) com abstrações personalizadas que facilitam o início da navegação dos alunos. 2. A [Extensão do Visual Studio Live Share](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) foi integrada a uma visualização do aluno para facilitar o acesso a assistentes de ensino e colegas de classe para ajuda e colaboração. 3. A [Extensão do GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) permite que os alunos vejam comentários de seus instrutores no editor. -### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %} -When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. Para obter mais informações consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +### Como iniciar a atividade em {% data variables.product.prodname_vscode_shortname %} +Ao criar uma atividade, {% data variables.product.prodname_vscode_shortname %} pode ser adicionado como editor preferido de uma atividade. Para obter mais informações consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". -This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click. +Isto incluirá um selo "Abrir em {% data variables.product.prodname_vscode_shortname %}" em todos os repositórios de alunos. Este selo processa a instalação de {% data variables.product.prodname_vscode_shortname %}, o pacote de extensão de sala de aula e a abertura ao trabalho ativo com um clique. {% note %} -**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. O aluno pode fazer o download do Git em [aqui](https://git-scm.com/downloads). +**Observaçãp:** O aluno deve ter o Git instalado no seu computador para fazer push do código de {% data variables.product.prodname_vscode_shortname %} para o seu repositório. Ele não é instalado automaticamente ao clicar no botão **Abrir em {% data variables.product.prodname_vscode_shortname %}**. O aluno pode fazer o download do Git em [aqui](https://git-scm.com/downloads). {% endnote %} ### Como usar o pacote de extensão GitHub Classroom A extensão GitHub Classroom tem dois componentes principais: a visualização "salas de aula" e a visualização "atividade ativa". -When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. +Quando o aluno lança a extensão pela primeira vez, ele é automaticamente transferido para a aba Explorador em {% data variables.product.prodname_vscode_shortname %}, onde pode ver a exibição de "Atividade ativa" ao lado da exibição em árvore de arquivos no repositório. ![Visão da atividade ativa do GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png) diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 9e431220d3..d51faea800 100644 --- a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -14,7 +14,7 @@ shortTitle: Extensões & integrações ## Ferramentas de edição -You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}. +Você pode se conectar a repositórios de {% data variables.product.product_name %} dentro de ferramentas de editor de terceiros, como o Atom, Unity e {% data variables.product.prodname_vs %}. ### {% data variables.product.product_name %} para Atom @@ -24,13 +24,13 @@ You can connect to {% data variables.product.product_name %} repositories within Você pode desenvolver em Unity, a plataforma de desenvolvimento de jogos de código aberto, e ver seu trabalho em {% data variables.product.product_name %}, usando a extensão de editor {% data variables.product.product_name %} para Unity. Para obter mais informações, consulte o [site](https://unity.github.com/) oficial da extensão de editor Unity ou a [documentação](https://github.com/github-for-unity/Unity/tree/master/docs). -### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} +### {% data variables.product.product_name %} para {% data variables.product.prodname_vs %} -With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). +Com {% data variables.product.product_name %} para a extensão de {% data variables.product.prodname_vs %}, você pode trabalhar em repositórios de {% data variables.product.product_name %} sem sair do {% data variables.product.prodname_vs %}. Para obter mais informações, consulte a extensão oficial do {% data variables.product.prodname_vs %} [site](https://visualstudio.github.com/) ou a [documentação](https://github.com/github/VisualStudio/tree/master/docs). -### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} +### {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_vscode %} -With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). +Com a extensão de {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_vscode %}, você pode revisar e gerenciar {% data variables.product.product_name %} pull requests em {% data variables.product.prodname_vscode_shortname %}. Para obter mais informações, consulte a extensão oficial do {% data variables.product.prodname_vscode_shortname %} [site](https://vscode.github.com/) ou a [documentação](https://github.com/Microsoft/vscode-pull-request-github). ## Ferramentas de gerenciamento de projetos diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index 0fc5a6ffd6..7ed47fca55 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -28,9 +28,9 @@ shortTitle: Editores de texto associados $ git config --global core.editor "atom --wait" ``` -## Using {% data variables.product.prodname_vscode %} as your editor +## Usando {% data variables.product.prodname_vscode %} como seu editor -1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +1. Instale [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" na documentação do {% data variables.product.prodname_vscode_shortname %}. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Digite este comando: ```shell @@ -68,9 +68,9 @@ shortTitle: Editores de texto associados $ git config --global core.editor "atom --wait" ``` -## Using {% data variables.product.prodname_vscode %} as your editor +## Usando {% data variables.product.prodname_vscode %} como seu editor -1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +1. Instale [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" na documentação do {% data variables.product.prodname_vscode_shortname %}. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Digite este comando: ```shell @@ -107,9 +107,9 @@ shortTitle: Editores de texto associados $ git config --global core.editor "atom --wait" ``` -## Using {% data variables.product.prodname_vscode %} as your editor +## Usando {% data variables.product.prodname_vscode %} como seu editor -1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +1. Instale [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" na documentação do {% data variables.product.prodname_vscode_shortname %}. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Digite este comando: ```shell diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 1e31a08bc6..e1c98c4005 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -61,11 +61,11 @@ Apenas os integrantes da organização com a função de *proprietário* ou *ger Uma conta corporativa permite que você gerencie centralmente as políticas e configurações para várias organizações {% data variables.product.prodname_dotcom %}, incluindo acesso de integrantes, cobrança e uso e segurança. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)". -#### 2. Creating an enterpise account +#### 2. Criando uma conta corporativa - {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." + Os clientes de {% data variables.product.prodname_ghe_cloud %} que pagam por fatura podem criar uma conta corporativa diretamente por meio de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte[Criando uma conta corporativa](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)". - {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you. + Os clientes de {% data variables.product.prodname_ghe_cloud %} que não pagam por fatura podem entrar em contato com a [equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact) para criar uma conta corporativa para você. #### 3. Adicionar organizações à conta corporativa diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md index 5aaf1081eb..6bba92902c 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -75,7 +75,7 @@ Para obter mais informações sobre como efetuar a autenticação em {% data var | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Acesse {% data variables.product.prodname_dotcom_the_website %} | Se você não precisar trabalhar com arquivos localmente, {% data variables.product.product_name %} permite que você realize a maioria das ações relacionadas ao Gits diretamente no navegador, da criação e bifurcação de repositórios até a edição de arquivos e abertura de pull requests. | Esse método é útil se você quiser uma interface visual e precisar fazer mudanças rápidas e simples que não requerem trabalho local. | | {% data variables.product.prodname_desktop %} | O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Para obter mais informações sobre como começar com {% data variables.product.prodname_desktop %}, consulte "[Primeiros passos com o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". | Este método é melhor se você precisa ou deseja trabalhar com arquivos localmente, mas preferir usar uma interface visual para usar o Git e interagir com {% data variables.product.product_name %}. | -| Editor de IDE ou de texto | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. Para obter mais informações, consulte "[Associando editores de texto ao Git](/github/using-git/associating-text-editors-with-git)". | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor. | +| Editor de IDE ou de texto | Você pode definir um editor de texto padrão, como [Atom](https://atom.io/) ou [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) para abrir e editar seus arquivos com Git, usar extensões e ver a estrutura do projeto. Para obter mais informações, consulte "[Associando editores de texto ao Git](/github/using-git/associating-text-editors-with-git)". | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor. | | Linha de comando, com ou sem {% data variables.product.prodname_cli %} | Para o controle e personalização mais granulares de como você usa o Git e interage com {% data variables.product.product_name %}, você pode usar a linha de comando. Para obter mais informações sobre como usar comandos do Git, consulte "[Folha de informações do Git](/github/getting-started-with-github/quickstart/git-cheatsheet).

{% data variables.product.prodname_cli %} é uma ferramenta separada de linha de comando separada que você pode instalar e que traz pull requests, problemas, {% data variables.product.prodname_actions %}, e outros recursos de {% data variables.product.prodname_dotcom %} para o seu terminal, para que você possa fazer todo o seu trabalho em um só lugar. Para obter mais informações, consulte "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Isto é muito conveniente se você já estiver trabalhando na linha de comando, o que permite que você evite mudar o contexto, ou se você estiver mais confortável usando a linha de comando. | | {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} tem uma API REST e uma API do GraphQL que você pode usar para interagir com {% data variables.product.product_name %}. Para obter mais informações, consulte "[Primeiros passos com a API](/github/extending-github/getting-started-with-the-api)". | A API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} seria muito útil se você quisesse automatizar tarefas comuns, fazer backup dos seus dados ou criar integrações que estendem {% data variables.product.prodname_dotcom %}. | ### 4. Escrevendo em {% data variables.product.product_name %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index c770b9af3d..c3b622682e 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -39,7 +39,7 @@ Siga estas etapas para aproveitar ao máximo a versão de avaliação: 1. [Crie uma organização](/enterprise-server@latest/admin/user-management/creating-organizations). 2. Para aprender as noções básicas de uso do {% data variables.product.prodname_dotcom %}, consulte: - - Webcast [Guia de início rápido do {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) + - [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast - [Entender o fluxo do {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow/) nos guias do {% data variables.product.prodname_dotcom %} - [Hello World](https://guides.github.com/activities/hello-world/) nos guias do {% data variables.product.prodname_dotcom %} - "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)" diff --git a/translations/pt-BR/content/get-started/using-github/github-mobile.md b/translations/pt-BR/content/get-started/using-github/github-mobile.md index 487072bd8f..3a03755c92 100644 --- a/translations/pt-BR/content/get-started/using-github/github-mobile.md +++ b/translations/pt-BR/content/get-started/using-github/github-mobile.md @@ -26,11 +26,11 @@ Com o {% data variables.product.prodname_mobile %} você pode: - Pesquisar, navegar e interagir com usuários, repositórios e organizações - Receber uma notificação push quando alguém mencionar seu nome de usuário {% ifversion fpt or ghec %}- Proteja sua conta do GitHub.com com autenticação de dois fatores -- Verify your sign in attempts on unrecognized devices{% endif %} +- Verifique suas tentativas de login em dispositivos não reconhecidos{% endif %} Para mais informações sobre notificações para {% data variables.product.prodname_mobile %}, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." -{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} +{% ifversion fpt or ghec %}- Para mais informações sobre a autenticação de dois fatores que usa {% data variables.product.prodname_mobile %}, consulte "[Configurando {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) e [Efetuando a autenticação usando {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)". {% endif %} ## Instalar o {% data variables.product.prodname_mobile %} @@ -48,7 +48,7 @@ Você pode estar conectado simultaneamente em um celular com uma conta pessoal e Você precisa instalar {% data variables.product.prodname_mobile %} 1.4 ou superior no seu dispositivo para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}. -Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} +Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. Para obter mais informações, consulte {% ifversion ghes %}"[Observações de versão](/enterprise-server/admin/release-notes)e {% endif %}"[Gerenciando {% data variables.product.prodname_mobile %} para a sua empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" na documentação de {% data variables.product.prodname_ghe_server %}.{% else %}."{% endif %} Durante o beta para {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, você deve estar conectado com uma conta pessoal em {% data variables.product.prodname_dotcom_the_website %}. @@ -76,9 +76,9 @@ Se você configurar o idioma do seu dispositivo para um idioma compatível, {% d {% data variables.product.prodname_mobile %} ativa automaticamente o Universal Links para iOS. Quando você clica em qualquer link {% data variables.product.product_name %}, a URL de destino vai abrir em {% data variables.product.prodname_mobile %} em vez do Safari. Para obter mais informações, consulte [Universal Links](https://developer.apple.com/ios/universal-links/) no site de desenvolvedor da Apple -To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. +Para desabilitar os links universais, pressione qualquer link de {% data variables.product.product_name %} e, em seguida, toque em **Abrir**. Toda vez que você clicar em um link {% data variables.product.product_name %} no futuro, o URL de destino será aberto no Safari em vez do {% data variables.product.prodname_mobile %}. -To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. +Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.product_name %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. ## Compartilhando feedback diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md index cde30dc308..ff32fcc3fd 100644 --- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md @@ -93,12 +93,12 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Command+B (Mac) ou
Ctrl+B (Windows/Linux) | Insere formatação Markdown para texto em negrito | | Command+I (Mac) ou
Ctrl+I (Windows/Linux) | Insere a formatação Markdown para texto em itálico{% ifversion fpt or ghae or ghes > 3.1 or ghec %} -| Command+E (Mac) ou
Ctrl+E (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %} -| Command+K (Mac) ou
Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} -| Command+V (Mac) or
Ctrl+V (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %} +| Command+E (Mac) ou
Ctrl+E (Windows/Linux) | Insere a formatação de Markdown para o código ou um comando dentro da linha{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %} +| Command+K (Mac) ou
Ctrl+K (Windows/Linux) | Insere a formatação de Markdown para criar um link{% endif %}{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} +| Command+V (Mac) ou
Ctrl+V (Windows/Linux) | Cria um link de Markdown quando aplicado sobre o texto destacado{% endif %} | Command+Shift+P (Mac) ou
Ctrl+Shift+P (Windows/Linux) | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae or ghes > 3.4 or ghec %} | Command+Shift+V (Mac) ou
Ctrl+Shift+V (Windows/Linux) | Cola o link HTML como texto simples{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -| Command+Shift+Opt+V (Mac) or
Ctrl+Shift+Alt+V (Windows/Linux) | Cola o link HTML como texto simples{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +| Command+Shift+Opt+V (Mac) ou
Ctrl+Shift+Alt+V (Windows/Linux) | Cola o link HTML como texto simples{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} | Command+Shift+7 (Mac) ou
Ctrl+Shift+7 (Windows/Linux) | Insere a formatação de Markdown para uma lista ordenada | | Command+Shift+8 (Mac) ou
Ctrl+Shift+8 (Windows/Linux) | Insere a formatação Markdown para uma lista não ordenada{% endif %} | Command+Enter (Mac) ou
Ctrl+Enter (Windows/Linux) | Envia um comentário | diff --git a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index af08755124..638fa805ad 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -31,17 +31,17 @@ Ao usar dois ou mais cabeçalhos, o GitHub gera automaticamente uma tabela de co ## Estilizar texto -You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files. +Você pode indicar o texto em destque, negrito, itálico, riscado, sublinhado ou sobrescrito nos campos de comentário e nos arquivos `.md` -| Estilo | Sintaxe | Atalho | Exemplo | Resultado | -| -------------------------- | -------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------ | -| Negrito | `** **` ou `__ __` | Command+B (Mac) ou Ctrl+B (Windows/Linux) | `**Esse texto está em negrito**` | **Esse texto está em negrito** | -| Itálico | `* *` ou `_ _`      | Command+I (Mac) ou Ctrl+I (Windows/Linux) | `*Esse texto está em itálico*` | *Esse texto está em itálico* | -| Tachado | `~~ ~~` | | `~~Esse texto estava errado~~` | ~~Esse texto estava errado~~ | -| Negrito e itálico aninhado | `** **` e `_ _` | | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** | -| Todo em negrito e itálico | `*** ***` | | `***Todo esse texto é importante***` | ***Todo esse texto é importante*** | -| Subscript | ` ` | | `This is a subscript text` | This is a subscript text | -| Superscript | ` ` | | `This is a superscript text` | This is a superscript text | +| Estilo | Sintaxe | Atalho | Exemplo | Resultado | +| -------------------------- | -------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------ | +| Negrito | `** **` ou `__ __` | Command+B (Mac) ou Ctrl+B (Windows/Linux) | `**Esse texto está em negrito**` | **Esse texto está em negrito** | +| Itálico | `* *` ou `_ _`      | Command+I (Mac) ou Ctrl+I (Windows/Linux) | `*Esse texto está em itálico*` | *Esse texto está em itálico* | +| Tachado | `~~ ~~` | | `~~Esse texto estava errado~~` | ~~Esse texto estava errado~~ | +| Negrito e itálico aninhado | `** **` e `_ _` | | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** | +| Todo em negrito e itálico | `*** ***` | | `***Todo esse texto é importante***` | ***Todo esse texto é importante*** | +| Sublinhado | ` ` | | `Este é um texto sublinhado` | Este é um texto de sublinhado | +| Sobrescrito | ` ` | | `Este é um texto sobrescrito` | Este é um texto sobrescrito | ## Citar texto @@ -92,7 +92,7 @@ Para obter mais informações, consulte "[Criar e destacar blocos de código](/a Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` e, em seguida, o URL entre parênteses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você também pode usar o atalho de teclado Command+K para criar um link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} Quando você tiver selecionado texto, você poderá colar um URL da sua área de transferência para criar automaticamente um link a partir da seleção.{% endif %} -{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut Command+V. If you'd like to replace the text with the link, use the keyboard shortcut Command+Shift+V.{% endif %} +{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} Você também pode criar um hiperlink de Markdown destacando o texto e usando o atalho de teclado Command+V. Se você deseja substituir o texto pelo link, use o atalho de teclado Command+Shift+V.{% endif %} `Este site foi construído usando [GitHub Pages](https://pages.github.com/).` @@ -238,11 +238,11 @@ Para obter mais informações, consulte "[Sobre listas de tarefas](/articles/abo ## Mencionar pessoas e equipes -Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando @ mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. For more information about notifications, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)." +Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando @ mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. Para obter mais informações sobre as notificações, consulte "[Sobre as notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)". {% note %} -**Note:** A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization. +**Observação:** Uma pessoa só será notificada sobre uma menção se a pessoa tiver acesso de leitura ao repositório e, se o repositório pertencer a uma organização, a pessoa é integrante da organização. {% endnote %} diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index f870386900..73ea6cb9a8 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -15,7 +15,7 @@ topics: ## Vinculando uma pull request a um problema -To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. Por exemplo, `Closes #10` ou `Fixes octo-org/octo-repo#100`. +Para vincular um pull request a um problema a mostre que uma correção está em andamento e para fechar o problema automaticamente quando alguém fizer merge do pull request, digite uma das palavras-chave a seguir seguida de uma referência ao problema. Por exemplo, `Closes #10` ou `Fixes octo-org/octo-repo#100`. * close * closes diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 6ff758e63f..81c7e8a51c 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -1,14 +1,14 @@ --- -title: Writing mathematical expressions -intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.' +title: Escrevendo expressões matemáticas +intro: 'Use o Markdown para exibir expressões matemáticas em {% data variables.product.company_short %}.' versions: feature: math -shortTitle: Mathematical expressions +shortTitle: Expressões matemáticas --- -To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. +Para habilitar uma comunicação clara de expressões matemáticas, {% data variables.product.product_name %} é compatível com a matemática formatada LaTeX dentro do Markdown. Para obter mais informações, consulte [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) no Wikibooks. -{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). +A capacidade de renderização matemática de {% data variables.product.company_short %} usa MathJax; um motor de exibição baseado em JavaScript. O MathJax é compatível com uma ampla variedade de macros de LaTeX e várias extensões de acessibilidade úteis. Para obter mais informações, consulte [a documentação do MathJax](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) e [a documentação de extensões de acessibilidade do MathJax](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). ## Writing inline expressions @@ -30,30 +30,30 @@ To add a math expression as a block, start a new line and delimit the expression $$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$ ``` -![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png) +![Expressão matemática como uma renderização de bloco](/assets/images/help/writing/math-expression-as-a-block-rendering.png) -## Writing dollar signs in line with and within mathematical expressions +## Como escrever sinais de dólar de acordo com e dentro de expressões matemáticas -To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly. +Para exibir um sinal de dólar como um caractere na mesma linha que uma expressão matemática, você deve escapar do não delimitador `$` para garantir que a linha seja renderizada corretamente. - - Within a math expression, add a `\` symbol before the explicit `$`. + - Dentro de uma expressão matemática, adicione um símbolo `\` antes do símbolo explícito `$`. ``` - This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$ + Essa expressão usa `\$` para mostrar um sinal do dólar: $\sqrt{\$4}$ ``` - ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png) + ![Sinal do dólar com expressão matemática](/assets/images/help/writing/dollar-sign-within-math-expression.png) - - Outside a math expression, but on the same line, use span tags around the explicit `$`. + - Fora de uma expressão matemática, mas na mesma linha, use tags de span em torno do `$ ` explícito. ``` - To split $100 in half, we calculate $100/2$ + Para dividir $100 pela metade, calculamos $100/2$ ``` ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png) ## Leia mais -* [The MathJax website](http://mathjax.org) +* [Site do MathJax](http://mathjax.org) * [Introdução à escrita e formatação no GitHub](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github) * [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md b/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md index da046bb0bf..76ec9153c4 100644 --- a/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md @@ -9,7 +9,7 @@ versions: ## Quais dados são coletados -Os dados coletados são descritos nos Termos de Telemetria de[{% data variables.product.prodname_copilot %}](/github/copilot/github-copilot-telemetry-terms)." Além disso, a extensão/plugin de {% data variables.product.prodname_copilot %} coleta a atividade do Ambiente Integrado de Desenvolvimento (IDE), vinculado a um registro de hora, e metadados coletados pelo pacote de telemetria da extensão/plugin. When used with {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. +Os dados coletados são descritos nos Termos de Telemetria de[{% data variables.product.prodname_copilot %}](/github/copilot/github-copilot-telemetry-terms)." Além disso, a extensão/plugin de {% data variables.product.prodname_copilot %} coleta a atividade do Ambiente Integrado de Desenvolvimento (IDE), vinculado a um registro de hora, e metadados coletados pelo pacote de telemetria da extensão/plugin. Quando usado com {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, ou outros IDEs, {% data variables.product.prodname_copilot %} coleta os metadados padrão fornecidos por esses IDEs. ## Como os dados são usados pelo {% data variables.product.company_short %} diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index 5c32b3b426..0467f0d8ae 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -30,7 +30,7 @@ Também é possível usar a barra de pesquisa "Filter cards" (Fitrar cartões) q - Filtrar cartões por status de verificação com `status:pending`, `status:success` ou `status:failure` - Filtrar cartões por tipo com `type:issue`, `type:pr` ou `type:note` - Filtrar cartões por estado e tipo com `is:open`, `is:closed` ou `is:merged`; e `is:issue`, `is:pr` ou `is:note` -- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` +- Filtrar cartões por problemas vinculados a um pull request por uma referência de fechamento usando `linked:pr` - Filtrar cartões por repositório em um quadro de projetos de toda a organização com `repo:ORGANIZATION/REPOSITORY` 1. Navegue até o quadro de projetos que contém os cartões que você deseja filtrar. diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md index 96fdbd457b..e4ebc4bb03 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md @@ -36,7 +36,7 @@ Para obter mais informações sobre os projetos, consulte {% ifversion fpt or gh ## Mantenha-se atualizado -Para manter-se atualizado sobre os comentários mais recentes em um problema, você pode assinar um problema para receber notificações sobre os comentários mais recentes. Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." +Para manter-se atualizado sobre os comentários mais recentes em um problema, você pode assinar um problema para receber notificações sobre os comentários mais recentes. Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para obter mais informações, consulte "[Sobre as notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" e "[Sobre o seu painel pessoal](/articles/about-your-personal-dashboard)". ## Gerenciamento da comunidade diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index d242bfcd66..cb296f4f05 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -27,7 +27,7 @@ shortTitle: Vincular PR a um problema ## Sobre problemas e pull requests vinculados -You can link an issue to a pull request manually or using a supported keyword in the pull request description. +Você pode vincular um problema a um pull request manualmente ou usar uma palavra-chave compatível na descrição do pull request. Quando você vincula uma pull request ao problema que a pull request tem de lidar, os colaboradores poderão ver que alguém está trabalhando no problema. @@ -57,7 +57,7 @@ A sintaxe para fechar palavras-chave depende se o problema está no mesmo reposi | Problema em um repositório diferente | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | Múltiplos problemas | Usar sintaxe completa para cada problema | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword. +Somente pull requests vinculados manualmente podem ser desvinculados. Para desvincular um problema que você vinculou usando uma palavra-chave, você deve editar a descrição da pull request para remover a palavra-chave. Você também pode usar palavras-chave de fechamento em uma mensagem de commit. O problema será encerrado quando você mesclar o commit no branch padrão, mas o pull request que contém o commit não será listado como um pull request vinculado. diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index 00cccc6cb2..7a0bd3cc10 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -25,4 +25,4 @@ Os painéis de problemas e pull requests estão disponíveis na parte superior d ## Leia mais -- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" +- "[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index c764ed65f7..83bbf89bc0 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ Na barra lateral esquerda do painel, é possível acessar os principais reposit Na seção "All activity" (Todas as atividades) do seu feed de notícias, você pode ver atualizações de outras equipes e repositórios em sua organização. -A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)." +A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. Para obter mais informações, consulte "[Sobre as notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" e "[Seguindo as pessoas](/articles/following-people)". Por exemplo, o feed de notícias da organização mostra atualizações quando alguém na organização: - Cria um branch. diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md index 3e79766081..e2b9d7dca2 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -40,13 +40,13 @@ Por padrão, se seu nome de usuário for mencionado em uma discussão de equipe, Para desativar notificações de discussões de equipe, você pode cancelar a assinatura de uma postagem de discussão específica ou alterar as configurações de notificação para cancelar a inspeção ou ignorar completamente discussões de uma equipe específica. É possível assinar para receber notificações de uma postagem de discussão específica se você estiver cancelando a inspeção de discussões dessa equipe. -For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" and "[Nested teams](/articles/about-teams/#nested-teams)." +Para obter mais informações, consulte "[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" e "[Equipes aninhadas](/articles/about-teams/#nested-teams)". {% ifversion fpt or ghec %} ## Discussões da organização -Você também pode usar discussões da organização para facilitar conversas em toda a sua organização. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)." +Você também pode usar discussões da organização para facilitar conversas em toda a sua organização. Para obter mais informações, consulte "[Habilitar ou desabilitar discussões no GitHub para uma organização](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)". {% endif %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 99a807cfd9..b456b79d4c 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -64,6 +64,6 @@ Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dot ## Leia mais -- "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" +- "[Referência da configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" - "[Sobre a autenticação de dois fatores e o SAML de logon único](/articles/about-two-factor-authentication-and-saml-single-sign-on)" - "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 77845a2118..5a355ae18e 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -58,4 +58,4 @@ Para obter mais informações sobre os provedores de identidade (IdPs) que {% da ## Leia mais - "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" +- "[Referência da configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index 7f2947696d..3951062745 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,7 +31,7 @@ As pessoas com o papel de mantenedor da equipe podem gerenciar as configuraçõe - [Excluir discussões de equipe](/articles/managing-disruptive-comments/#deleting-a-comment) - [Adicionar integrantes da organização à equipe](/articles/adding-organization-members-to-a-team) - [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team) -- Remove the team's access to repositories +- Removea o acesso da equipe aos repositórios - [Gerenciar atribuição de código para a equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [Gerenciar lembretes agendados para pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} diff --git a/translations/pt-BR/content/pages/index.md b/translations/pt-BR/content/pages/index.md index daf96fb0a7..65f9aa86bc 100644 --- a/translations/pt-BR/content/pages/index.md +++ b/translations/pt-BR/content/pages/index.md @@ -1,7 +1,7 @@ --- title: Documentação do GitHub Pages shortTitle: GitHub Pages -intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' +intro: 'Aprenda a criar um site diretamente em um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore ferramentas de criação de sites como o Jekyll e problemas de resolução de problemas com seu site {% data variables.product.prodname_pages %}.' introLinks: quickstart: /pages/quickstart overview: /pages/getting-started-with-github-pages/about-github-pages diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index d04cb47436..01453ac638 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -24,7 +24,7 @@ topics: ### Mesclar mensagem para uma mesclagem por squash -When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. +Ao fazer combinação por squash e merge, {% data variables.product.prodname_dotcom %} gera uma mensagem de commit padrão, que você pode editar. A mensagem padrão depende do número de commits no pull request, que não inclui commits de merge. | Número de commits | Sumário | Descrição | | ----------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | @@ -32,7 +32,7 @@ When you squash and merge, {% data variables.product.prodname_dotcom %} generate | Mais de um commit | Título da pull request, seguido do número da pull request | Uma lista das mensagens de commit para todos os commits combinados por squash, por ordem de data | {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %} -People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". +As pessoas com acesso de administrador a um repositório podem configurar o repositório para usar o título do pull request como a mensagem de merge padrão para todos os commits combinados por squash. Para obter mais informações, consulte "[Configurar o commit combinado por squash](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". {% endif %} ### Fazendo combinação por squash e merge com um branch de longa duração diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index b911a029d8..b8cca3ec54 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: Alterar o stage de uma pull request -intro: You can mark a draft pull request as ready for review or convert a pull request to a draft. +intro: Você pode marcar um pull request como pronto para revisão ou converter um pull request em um rascunho. permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index 105a52725b..3c8a58e972 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -21,7 +21,7 @@ Os repositórios pertencem a uma conta pessoal (um único proprietário) ou a um Para atribuir um revisor a um pull request, você precisará de acesso de gravação ao repositório. Para obter mais informações sobre o acesso do repositório, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". Se você tiver acesso de gravação, você pode atribuir a qualquer pessoa que tenha acesso de leitura ao repositório como revisor. -Os integrantes da organização com acesso de gravação também podem atribuir um comentário de pull request a qualquer pessoa ou equipe com acesso de leitura a um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." +Os integrantes da organização com acesso de gravação também podem atribuir um comentário de pull request a qualquer pessoa ou equipe com acesso de leitura a um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. Se você solicitar uma revisão de uma equipe e a atividade de revisão de código estiver habilitada, serão solicitados membros específicos e a equipe será removida como revisora. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." {% note %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index ae7434e7b7..8ce6abb5dc 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -22,7 +22,7 @@ Após a abertura de uma pull request, qualquer pessoa com acesso *de leitura* po {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)". You can specify a subset of team members to be automatically assigned in the place of the whole team. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." +Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)". Você pode especificar um subconjunto de integrantes da equipe a ser atribuído automaticamente no lugar de toda equipe. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." As revisões permitem discussão das alterações propostas e ajudam a garantir que as alterações atendam às diretrizes de contribuição do repositório e outros padrões de qualidade. Você pode definir quais indivíduos ou equipes possuem determinados tipos de área de código em um arquivo CODEOWNERS. Quando uma pull request modifica código que tem um proprietário definido, esse indivíduo ou equipe será automaticamente solicitado como um revisor. Para obter mais informações, consulte "[Sobre proprietários de código](/articles/about-code-owners/)". diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index 7429d93c11..31050aeaeb 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -31,9 +31,9 @@ Veja a seguir um exemplo de uma [comparação entre dois branches](https://githu ## Comparar tags -A comparação de tags de versão irá mostrar alterações no seu repositório desde a última versão. For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)." +A comparação de tags de versão irá mostrar alterações no seu repositório desde a última versão. Para obter mais informações, consulte "[Comparando versões](/github/administering-a-repository/comparing-releases). -To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page. +Para comparar tags, você pode selecionar um nome de tag no menu suspenso `Comparar` na parte superior da página. Veja a seguir o exemplo de uma [comparação entre duas tags](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 9e64f711fc..e1d8fdeed0 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -63,9 +63,9 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n - Opcionalmente, para ignorar uma revisão de aprovação de pull request quando um commit de modificação de código for enviado por push para o branch, selecione **Ignorar aprovações obsoletas de pull request quando novos commits forem enviados por push**. ![Caixa de seleção Dismiss stale pull request approvals when new commits are pushed (Ignorar aprovações de pull requests obsoletas ao fazer push de novos commits)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - Opcionalmente, para exigir a revisão de um proprietário do código quando o pull request afeta o código que tem um proprietário designado, selecione **Exigir revisão de Proprietários do Código**. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". ![Require review from code owners (Exigir revisão de proprietários de código)](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} + - Opcionalmente, para permitir que os atores específicos façam push de código para o branch sem criar pull requests, quando necessário, selecione **Permitir que os atores especificados ignorem os pull requests necessários**. Em seguida, procure e selecione os atores que devem ter permissão para ignorar a criação de um pull request. ![Permitir os atores específicos que podem ignorar a caixa de seleção de exigências do pull request]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} {% endif %} - - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Then, search for and select the actors who are allowed to dismiss pull request reviews. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} + - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Em seguida, pesquise e selecione os atores que têm permissão para ignorar as revisões do pull request. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Restringir quem pode ignorar a caixa de seleção de revisões de pull request]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} 1. Opcionalmente, habilite as verificações de status obrigatórias. Para obter mais informações, consulte "[Sobre verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)". - Selecione **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge). ![Opção Required status checks (Verificações de status obrigatórias)](/assets/images/help/repository/required-status-checks.png) - Opcionalmente, para garantir que os pull requests sejam testados com o código mais recente no branch protegido, selecione **Exigir que os branches estejam atualizados antes do merge**. ![Caixa de seleção Status obrigatório rígido ou flexível](/assets/images/help/repository/protecting-branch-loose-status.png) @@ -95,7 +95,7 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Em seguida, escolha quem pode fazer push forçado no branch. - Selecione **Todos** para permitir que todos com pelo menos permissões de escrita no repositório para forçar push para o branch, incluindo aqueles com permissões de administrador. - - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} + - Selecione **Especificar quem podefazer push forçado** para permitir que apenas atores específicos façam push forçado no branch. Em seguida, pesquise e selecione esses atores. ![Captura de tela das opções para especificar que pode fazer push forçado]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} {% endif %} Para obter mais informações sobre push forçado, consulte "[Permitir pushes forçados](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)". diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md index b1594861d4..ead476ddd5 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -52,7 +52,7 @@ Ao criar um repositório, você pode optar por tornar o repositório público ou {% elsif ghae %} -When you create a repository owned by your personal account, the repository is always private. Ao criar um repositório pertencente a uma organização, você pode optar por tornar o repositório privado ou interno. +Ao criar um repositório pertencente à sua conta pessoal, o repositório é sempre privado. Ao criar um repositório pertencente a uma organização, você pode optar por tornar o repositório privado ou interno. {% endif %} @@ -90,7 +90,7 @@ Todos os integrantes da empresa têm permissões de leitura no repositório inte {% data reusables.repositories.internal-repo-default %} -Qualquer integrante da empresa pode bifurcar qualquer repositório interno pertencente a uma organização da empresa. The forked repository will belong to the member's personal account, and the visibility of the fork will be private. Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente. +Qualquer integrante da empresa pode bifurcar qualquer repositório interno pertencente a uma organização da empresa. O repositório bifurcado pertencerá à conta pessoal do integrante e a visibilidade da bifurcação será privada. Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente. {% endif %} ## Limites para visualização de conteúdo e diffs no repositório diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index 30de098bf0..30a90c6c95 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: Criar um repositório de modelos -intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.' +intro: 'Você pode converter um repositório existente em um modelo para que você e outras pessoas possam gerar novos repositórios com a mesma estrutura de diretório, branche, e arquivos.' permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -24,7 +24,7 @@ shortTitle: Criar um repositório de modelo Para criar um repositório de modelos, é preciso criar um repositório e, em seguida, torná-lo um modelo. Para obter mais informações sobre como criar um repositório, consulte "[Criar um repositório](/articles/creating-a-new-repository)". -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". +Depois que seu repositório se tornar um modelo, qualquer pessoa com acesso ao repositório poderá gerar um novo repositório com a mesma estrutura do diretório e arquivos do seu branch padrão. Eles também podem optar por incluir todos os outros branches no seu repositório. Os branches criados a partir de um modelo têm histórico não relacionado, o que significa que você não pode criar pull requests ou fazer merge entre os branches. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md index fd257679dd..767655ad08 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md @@ -29,7 +29,7 @@ Os {% data reusables.organizations.owners-and-admins-can %} excluem um repositó {% endwarning %} -Some deleted repositories can be restored within {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif%} days of deletion. {% ifversion ghes or ghae %}O administrador do seu site pode ser capaz de restaurar um repositório excluído para você. Para obter mais informações, consulte "[Restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". {% else %}Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %} +Alguns repositórios excluídos podem ser restaurados em {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif%} dias de exclusão. {% ifversion ghes or ghae %}O administrador do seu site pode ser capaz de restaurar um repositório excluído para você. Para obter mais informações, consulte "[Restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". {% else %}Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md index bb5a7ab252..6982c98867 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md @@ -39,7 +39,7 @@ Se você planeja renomear um repositório que tenha um site do {% data variables {% note %} -**Observação:** {% data variables.product.prodname_dotcom %} não irá redirecionar chamadas para uma ação hospedada por um repositório renomeado. Qualquer fluxo de trabalho que usar essa ação falhará com o erro `repositório não encontrado`. Instead, create a new repository and action with the new name and archive the old repository. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". +**Observação:** {% data variables.product.prodname_dotcom %} não irá redirecionar chamadas para uma ação hospedada por um repositório renomeado. Qualquer fluxo de trabalho que usar essa ação falhará com o erro `repositório não encontrado`. Em vez disso, crie um novo repositório e ação com o novo nome e arquive o repositório antigo. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". {% endnote %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 291310e7ca..e2afef891a 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -28,7 +28,7 @@ topics: Quando você transfere um repositório para um novo proprietário, ele pode administrar imediatamente o conteúdo do repositório, além de problemas, pull requests, versões, quadros de projeto e configurações. Pré-requisitos para transferências no repositório: -- When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. Se o novo proprietário não aceitar a transferência em um dia, o convite vai expirar.{% endif %} +- Ao transferir um repositório que possui para outra conta pessoal, o novo proprietário receberá um e-mail de confirmação.{% ifversion fpt or ghec %} O e-mail de confirmação inclui instruções para aceitar a transferência. Se o novo proprietário não aceitar a transferência em um dia, o convite vai expirar.{% endif %} - Para transferir um repositório que você possui para uma organização, é preciso ter permissão para criar um repositório na organização de destino. - A conta de destino não deve ter um repositório com o mesmo nome ou uma bifurcação na mesma rede. - O proprietário original do repositório é adicionado como colaborador no repositório transferido. Outros colaboradores no repositório transferido permanecem intactos.{% ifversion ghec or ghes or ghae %} @@ -44,7 +44,7 @@ Quando você transfere um repositório, também são transferidos problemas, pul - Se o repositório transferido for uma bifurcação, continuará associado ao repositório upstream. - Se o repositório transferido tiver alguma bifurcação, ela permanecerá associada ao repositório depois que a transferência for concluída. - Se o repositório transferido usar {% data variables.large_files.product_name_long %}, todos os objetos {% data variables.large_files.product_name_short %} serão automaticamente movidos. Esta transferência ocorre em segundo plano. Portanto, se você tiver um número grande de objetos de {% data variables.large_files.product_name_short %} ou se os próprios objetos de {% data variables.large_files.product_name_short %} forem grandes, poderá levar um tempo para realizar a transferência.{% ifversion fpt or ghec %} Antes de transferir um repositório que usa {% data variables.large_files.product_name_short %}, certifique-se de que a conta de recebimento tenha pacotes de dados suficientes para armazenar os objetos de {% data variables.large_files.product_name_short %} que você vai se transferir. Para obter mais informações sobre como adicionar armazenamento para contas pessoais, consulte "[Atualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)".{% endif %} -- When a repository is transferred between two personal accounts, issue assignments are left intact. When you transfer a repository from a personal account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Somente proprietários da organização têm permissão para criar novas atribuições de problemas. When you transfer a repository from an organization to a personal account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed. +- Quando um repositório é transferido entre duas contas pessoais, as atribuições de problemas são mantidas intactas. Quando você transfere um repositório de uma conta pessoal para uma organização, os problemas atribuídos a integrantes da organização permanecem intactos, e todos os outros responsáveis por problemas são destituídos. Somente proprietários da organização têm permissão para criar novas atribuições de problemas. Quando você transfere um repositório de uma organização para uma conta pessoal, são mantidos somente os problemas atribuídos ao proprietário do repositório. Todos os outros responsáveis por problemas são removidos. - Se o repositório transferido contiver um site do {% data variables.product.prodname_pages %}, os links para o repositório do Git na web e por meio de atividade do Git serão redirecionados. No entanto, não redirecionamos o {% data variables.product.prodname_pages %} associado ao repositório. - Todos os links para o local do repositório anterior são automaticamente redirecionados para o novo local. Quando você usar `git clone`, `git fetch` ou `git push` em um repositório transferido, esses comandos serão redirecionados para a nova URL ou local do repositório. No entanto, para evitar confusão, recomendamos que qualquer clone local seja atualizado para apontar para a nova URL do repositório. Use `git remote` na linha de comando para fazer isso: @@ -52,7 +52,7 @@ Quando você transfere um repositório, também são transferidos problemas, pul $ git remote set-url origin new_url ``` -- When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %} +- Quando você transfere um repositório de uma organização para uma conta pessoal, os colaboradores somente leitura do repositório não serão transferidos. Isso acontece porque os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta pessoal. Para mais informações sobre os níveis de permissão do repositório, consulte "[Níveis de permissão para um repositório de conta pessoal](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).{% ifversion fpt or ghec %} - Os patrocinadores que têm acesso ao repositório por meio de um nível de patrocínio podem ser afetados. Para obter mais informações, consulte "[Adicionando um repositório a uma camada de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %} Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". @@ -65,7 +65,7 @@ Depois que um repositório for transferido para uma organização, os privilégi ## Transferir um repositório pertencente à sua conta pessoal -You can transfer your repository to any personal account that accepts your repository transfer. When a repository is transferred between two personal accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository. +É possível transferir seu repositório para qualquer conta pessoal que aceite transferência de repositório. Quando um repositório é transferido entre duas contas pessoais, o proprietário e os colaboradores do repositório original são automaticamente adicionados como colaboradores ao novo repositório. {% ifversion fpt or ghec %}Se você publicou um site {% data variables.product.prodname_pages %} em um repositório privado e adicionou um domínio personalizado, antes de transferir o repositório, você deverá remover ou atualizar seus registros DNS para evitar o risco de tomada de um domínio. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} @@ -75,9 +75,9 @@ You can transfer your repository to any personal account that accepts your repos ## Transferir um repositório pertencente à organização -If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your personal account or to another organization. +Se você tiver permissões de proprietário em uma organização ou permissões de administrador para um dos repositórios dela, poderá transferir um repositório pertencente à organização para sua conta pessoal ou para outra organização. -1. Sign into your personal account that has admin or owner permissions in the organization that owns the repository. +1. Entre na sua conta pessoal que tem permissões de proprietário ou de administrador na organização proprietária do repositório. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.transfer-repository-steps %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 3c8406b9d2..e5b7bce385 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.3' - ghae: issue-4651 + ghae: '*' ghec: '*' topics: - Repositories diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 7d9797399d..2a39f4a96f 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -50,7 +50,7 @@ Para reduzir o tamanho do seu arquivo CODEOWNERS, considere o uso de padrões cu Um arquivo CODEOWNERS usa um padrão que segue a maioria das mesmas regras usadas nos arquivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), com [algumas exceções](#syntax-exceptions). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Os usuários devem ter acessso de `leitura` ao repositório e as equipes devem ter acesso explícito de `gravação`, mesmo que os integrantes da equipe já tenham acesso. -{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.product.prodname_managed_user %}. For more information about {% data variables.product.prodname_managed_users %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +{% ifversion fpt or ghec%}Na maioria dos casos você{% else %}Você{% endif %} também pode se referir a um usuário por um endereço de e-mail que foi adicionado a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, por exemplo, `user@example tom`. {% ifversion fpt or ghec %} Você não pode usar um endereço de e-mail para fazer referência a um {% data variables.product.prodname_managed_user %}. Para obter mais informações sobre {% data variables.product.prodname_managed_users %}, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}{% endif %} Os caminhos dos CODEOWNERS diferenciam maiúsculas de minúsculas, porque {% data variables.product.prodname_dotcom %} usa um sistema de arquivos que diferencia maiúsculas e minúsculas. Uma vez que os CODEOWNERS são avaliados por {% data variables.product.prodname_dotcom %}, até mesmo sistemas que diferenciam maiúsculas de minúsculas (por exemplo, macOS) devem usar caminhos e arquivos que são tratados corretamente no arquivo dos CODEOWNERS. diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index 1f297da085..d74e401fb3 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -29,9 +29,9 @@ Um README, muitas vezes, é o primeiro item que um visitante verá ao visitar se - Onde os usuários podem obter ajuda com seu projeto - Quem mantém e contribui com o projeto -If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors. +Se você colocar o seu arquivo README no `.github` oculto do seu repositório, raiz ou diretório de `docs`, {% data variables.product.product_name %} irá reconhecer e automaticamente supervisionar seu README para os visitantes do repositório. -If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory. +Se um repositório contiver mais de um arquivo README, o arquivo mostrado será escolhido entre os locais na seguinte ordem: o diretório do `.github`, em seguida, o diretório raiz do repositório e, finalmente, o diretório `docs`. ![Página principal do repositório github/scientist e seu arquivo README](/assets/images/help/repository/repo-with-readme.png) diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md index a50e53bc9c..396deb8978 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md @@ -17,13 +17,13 @@ shortTitle: Pré-visualização de mídias sociais Até você adicionar uma imagem, os links de repositório se expandem para mostrar informações básicas sobre o repositório e o avatar do proprietário. Adicionar uma imagem ao repositório ajuda a identificar seu projeto em várias plataformas sociais. -## Adding an image to customize the social media preview of your repository +## Adicionar uma imagem para personalizar a visualização de mídia social do seu repositório {% ifversion not ghae %}Você pode fazer o upload de uma imagem para um repositório privado, mas sua imagem só pode ser compartilhada a partir de um repositório público.{% endif %} {% tip %} -**Tip:** Your image should be a PNG, JPG, or GIF file under 1 MB in size. Para renderização de melhor qualidade, é recomendável manter a imagem em 640 x 320 pixels. +**Dica:** Sua imagem deve ser um arquivo PNG, JPG ou GIF com tamanho inferiro a 1 MB. Para renderização de melhor qualidade, é recomendável manter a imagem em 640 x 320 pixels. {% endtip %} @@ -35,15 +35,15 @@ Até você adicionar uma imagem, os links de repositório se expandem para mostr ![Menu suspenso Social preview (Visualização social)](/assets/images/help/repository/social-preview.png) -## About transparency +## Sobre transparência -We support PNG images with transparency. Many communication platforms support a dark mode, so using a transparent social preview may be beneficial. The transparent image below is acceptable on a dark background; however, this may not always be the case. +Fornecemos compatibilidade para as imagens PNG com transparência. Muitas plataformas de comunicação são compatíveis com um modo escuro, por isso usar uma visualização social transparente pode ser benéfico. A imagem transparente abaixo é aceitável num fundo escuro; no entanto, é possível que nem sempre seja assim. -When using an image with transparency, keep in mind how it may look on different color backgrounds or platforms that don't support transparency. +Ao usar uma imagem com transparência, tenha em mente como ela pode aparecer em planos de cor diferentes ou plataformas que não são compatíveis com a transparência. {% tip %} -**Tip:** If you aren't sure, we recommend using an image with a solid background. +**Dica:** Se você não tiver certeza, recomendamos o uso de uma imagem com um fundo sólido. {% endtip %} -![Social preview transparency](/assets/images/help/repository/social-preview-transparency.png) +![Transparência de pré-visualização social](/assets/images/help/repository/social-preview-transparency.png) diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md index 5d947c0cbd..44a705c657 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md @@ -58,7 +58,7 @@ custom: ["https://www.paypal.me/octocat", octocat.com] {% endnote %} -You can create a default sponsor button for your organization or personal account. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." +Você pode criar um botão de patrocinador padrão para sua organização ou conta pessoal. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% note %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md index 3145ced99c..152b0d7e1c 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -19,7 +19,7 @@ shortTitle: Discussions {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} 1. Para desabilitar as discussões, em "Recursos", desmarque **Discussões**. -You can also use organization discussions to facilitate conversations that span multiple repositories in your organization. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)." +Você também pode usar discussões da organização para facilitar conversas que abrangem vários repositórios na sua organização. Para obter mais informações, consulte "[Habilitar ou desabilitar discussões no GitHub para uma organização](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)". ## Leia mais diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index f5853b408e..1d3dfddc5b 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -29,11 +29,11 @@ miniTocMaxHeadingLevel: 3 É possível habilitar o {% data variables.product.prodname_actions %} para seu repositório. {% data reusables.actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para o seu repositório completamente. {% data reusables.actions.disabled-actions-description %} -Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions {% if actions-workflow-policy %}and reusable workflows{% endif %} a workflow can run. +Como alternativa, você pode habilitar {% data variables.product.prodname_actions %} em seu repositório, mas limitar as ações {% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} que um fluxo de trabalho pode ser executado. ## Gerenciando as permissões do {% data variables.product.prodname_actions %} para o seu repositório -You can disable {% data variables.product.prodname_actions %} for a repository, or set a policy that configures which actions{% if actions-workflow-policy %} and reusable workflows{% endif %} can be used in the repository. +Você pode desabilitar {% data variables.product.prodname_actions %} para um repositório ou definir uma política que configura quais ações{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} podem ser usados no repositório. {% note %} @@ -49,9 +49,9 @@ You can disable {% data variables.product.prodname_actions %} for a repository, {% indented_data_reference reusables.actions.actions-use-policy-settings spaces=3 %} {% if actions-workflow-policy %} - ![Set actions policy for this repository](/assets/images/help/repository/actions-policy-with-workflows.png) + ![Definir política de ações para este repositório](/assets/images/help/repository/actions-policy-with-workflows.png) {%- else %} - ![Set actions policy for this repository](/assets/images/help/repository/actions-policy.png) + ![Definir política de ações para este repositório](/assets/images/help/repository/actions-policy.png) {%- endif %} 1. Clique em **Salvar**. @@ -60,7 +60,7 @@ You can disable {% data variables.product.prodname_actions %} for a repository, {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions-general %} -1. Under "Actions permissions", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions to the list. +1. Em "Permissões de ações", selecione {% data reusables.actions.policy-label-for-select-actions-workflows %} e adicione suas ações necessárias à lista. {% if actions-workflow-policy%} ![Adicionar ações e fluxos de trabalho reutilizáveis à lista de permissões](/assets/images/help/repository/actions-policy-allow-list-with-workflows.png) @@ -106,14 +106,14 @@ Se uma política estiver desabilitada para uma organização {% ifversion ghec o {% data reusables.actions.workflow-permissions-intro %} -As permissões padrão também podem ser configuradas nas configurações da organização. If your repository belongs to an organization and a more restrictive default has been selected in the organization settings, the same option is selected in your repository settings and the permissive option is disabled. +As permissões padrão também podem ser configuradas nas configurações da organização. Se o seu repositório pertence a uma organização e um padrão mais restritivo foi selecionado nas configurações da organização, a mesma opção está selecionada nas configurações do repositório e a opção permissiva será desabilitada. {% data reusables.actions.workflow-permissions-modifying %} ### Configurar as permissões padrão do `GITHUB_TOKEN` {% if allow-actions-to-approve-pr-with-ent-repo %} -By default, when you create a new repository in your personal account, `GITHUB_TOKEN` only has read access for the `contents` scope. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings. +Por padrão, ao criar um novo repositório na sua conta pessoal, `GITHUB_TOKEN` só terá acesso de leitura para o escopo `conteúdo`. Se você criar um novo repositório em uma organização, a configuração será herdada do que está configurado nas configurações da organização. {% endif %} {% data reusables.repositories.navigate-to-repo %} @@ -130,7 +130,7 @@ By default, when you create a new repository in your personal account, `GITHUB_T {% data reusables.actions.workflow-pr-approval-permissions-intro %} -By default, when you create a new repository in your personal account, workflows are not allowed to create or approve pull requests. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings. +Por padrão, ao cria um novo repositório na sua conta pessoal, os fluxos de trabalho não são autorizados a criar ou aprovar pull requests. Se você criar um novo repositório em uma organização, a configuração será herdada do que está configurado nas configurações da organização. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -179,16 +179,16 @@ Você também pode definir um período de retenção personalizado para um artef {% if actions-cache-policy-apis %} -## Configuring cache storage for a repository +## Configurando armazenamento em cache para um repositório -{% data reusables.actions.cache-default-size %} However, these default sizes might be different if an enterprise owner has changed them. {% data reusables.actions.cache-eviction-process %} +{% data reusables.actions.cache-default-size %} No entanto, esses tamanhos padrão podem ser diferentes se um proprietário da empresa os alterou. {% data reusables.actions.cache-eviction-process %} -You can set a total cache storage size for your repository up to the maximum size allowed by the enterprise policy setting. +É possível definir um tamanho de armazenamento total de cache para seu repositório até o tamanho máximo permitido pela configuração da política corporativa. -The repository settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API: +As configurações do repositório para o armazenamento de cache {% data variables.product.prodname_actions %} atualmente só podem ser modificadas usando a API REST: -* To view the current cache storage limit for a repository, see "[Get GitHub Actions cache usage policy for a repository](/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository)." -* To change the cache storage limit for a repository, see "[Set GitHub Actions cache usage policy for a repository](/rest/actions/cache#set-github-actions-cache-usage-policy-for-a-repository)." +* Para visualizar o limite atual de armazenamento de cache para um repositório, consulte "[Obter política de uso do cache do GitHub Actions para um repositório](/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository)". +* Para alterar o limite de armazenamento de cache para um repositório, consulte "[Definir política de uso do cache do GitHub Actions para um repositório](/rest/actions/cache#set-github-actions-cache-usage-policy-for-a-repository)". {% data reusables.actions.cache-no-org-policy %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md index 91f6c9677b..ba2eab49f6 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md @@ -16,7 +16,7 @@ versions: {% endnote %} -Quando você adiciona uma regra de proteção de tags, todas as tags que correspondem ao padrão fornecido serão protegidas. Somente usuários com permissões de administrador ou de manutenção no repositório poderão criar tags protegidas, e apenas usuários com permissões de administrador no repositório poderão excluir tags protegidas. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role)". {% data variables.product.prodname_github_apps %} require the `Repository administration: write` permission to modify a protected tag. +Quando você adiciona uma regra de proteção de tags, todas as tags que correspondem ao padrão fornecido serão protegidas. Somente usuários com permissões de administrador ou de manutenção no repositório poderão criar tags protegidas, e apenas usuários com permissões de administrador no repositório poderão excluir tags protegidas. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role)". {% data variables.product.prodname_github_apps %} exige a permissão `Repository administration: write` para modificar uma tag protegida. {% if custom-repository-roles %} Além disso, você pode criar funções personalizadas de repositórios para permitir que outros grupos de usuários criem ou excluam tags que correspondem às regras de proteção de tags. Para obter mais informações, consulte "[Gerenciando funções de repositórios personalizados para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".{% endif %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md index 4c9137f938..6651401007 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -15,7 +15,7 @@ redirect_from: ## Sobre os objetos {% data variables.large_files.product_name_short %} nos arquivos -O {% data variables.product.product_name %} cria arquivos de código-fonte do seu repositório na forma de arquivos ZIP e tarballs. As pessoas podem baixar esses arquivos na página principal do seu repositório ou como ativos de versão. Por padrão, os objetos {% data variables.large_files.product_name_short %} não estão incluídos nesses arquivos, apenas os arquivos de ponteiro para esses objetos. Para melhorar a usabilidade dos arquivos no seu repositório, você pode optar por incluir os objetos do {% data variables.large_files.product_name_short %}. To be included, the {% data variables.large_files.product_name_short %} objects must be covered by tracking rules in a *.gitattributes* file that has been committed to the repository. +O {% data variables.product.product_name %} cria arquivos de código-fonte do seu repositório na forma de arquivos ZIP e tarballs. As pessoas podem baixar esses arquivos na página principal do seu repositório ou como ativos de versão. Por padrão, os objetos {% data variables.large_files.product_name_short %} não estão incluídos nesses arquivos, apenas os arquivos de ponteiro para esses objetos. Para melhorar a usabilidade dos arquivos no seu repositório, você pode optar por incluir os objetos do {% data variables.large_files.product_name_short %}. Para serem incluídos, os objetos de {% data variables.large_files.product_name_short %} devem ser cobertos pelas regras de rastreamento em um arquivo *.gitattributes* que teve commit no repositório. Sevocê optar por incluir os objetos {% data variables.large_files.product_name_short %} nos arquivos de seu repositório, cada download desses arquivos contará para o uso de largura de banda de sua conta. Cada conta recebe {% data variables.large_files.initial_bandwidth_quota %} por mês de largura de banda gratuitamente, e você pode pagar pelo uso adicional. Para obter mais informações, consulte "[Sobre armazenamento e uso de largura de banda](/github/managing-large-files/about-storage-and-bandwidth-usage)" e "[Gerenciando a cobrança para {% data variables.large_files.product_name_long %}](/billing/managing-billing-for-git-large-file-storage)". diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 618ab3e634..4b4d435499 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -24,7 +24,7 @@ Os proprietários da organização podem restringir a capacidade de alterar a vi {% ifversion ghec %} -Members of an {% data variables.product.prodname_emu_enterprise %} can only set the visibility of repositories owned by their personal account to private, and repositories in their enterprise's organizations can only be private or internal. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +Os membros de um {% data variables.product.prodname_emu_enterprise %} só podem definir a visibilidade de repositórios pertencentes à sua conta pessoalcomo privada, e os repositórios das organizações de sua empresa só podem ser privados ou internos. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% endif %} @@ -52,7 +52,7 @@ Recomendamos revisar as seguintes advertências antes de alterar a visibilidade {%- endif %} {%- ifversion fpt %} -* If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Qualquer site publicado do {% data variables.product.prodname_pages %} terá sua publicação cancelada automaticamente. Se você adicionou um domínio personalizado ao site do {% data variables.product.prodname_pages %}, deverá remover ou atualizar os registros de DNS antes de tornar o repositório privado para evitar o risco de uma aquisição de domínio. Para obter mais informações, consulte "[Produtos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products) e "[Gerenciando um domínio personalizado para o seu site de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +* Se você estiver usando {% data variables.product.prodname_free_user %} para contas pessoais ou organizações, algumas funcionalidades não estarão disponíveis no repositório depois de alterar a visibilidade para privada. Qualquer site publicado do {% data variables.product.prodname_pages %} terá sua publicação cancelada automaticamente. Se você adicionou um domínio personalizado ao site do {% data variables.product.prodname_pages %}, deverá remover ou atualizar os registros de DNS antes de tornar o repositório privado para evitar o risco de uma aquisição de domínio. Para obter mais informações, consulte "[Produtos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products) e "[Gerenciando um domínio personalizado para o seu site de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". {%- endif %} {%- ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md index f6373ee621..428f0e0e4d 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md @@ -32,4 +32,5 @@ Se você criar um URL inválido usando parâmetros de consulta, ou se não tiver ## Leia mais -- "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating an issue from a URL query](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-url-query)" +- "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request/)" diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/creating-new-files.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/creating-new-files.md index 44626d1e60..94c0901612 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-files/creating-new-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/creating-new-files.md @@ -16,7 +16,7 @@ topics: Ao criar um arquivo no {% data variables.product.product_name %}, lembre-se do seguinte: -- If you try to create a new file in a repository that you don’t have access to, we will fork the project to your personal account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. +- Se você tentar criar um arquivo em um repositório ao qual não tem acesso, bifurcaremos o projeto para sua conta pessoal e ajudaremos você a enviar [um pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) para o repositório original depois que fizer o commit da alteração. - Os nomes de arquivos criados por meio da interface da web podem conter apenas caracteres alfanuméricos e hífens (`-`). Para usar outros caracteres, [crie e faça commit dos arquivos localmente e, em seguida, faça push deles no repositório do {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository-using-the-command-line). {% data reusables.repositories.sensitive-info-warning %} diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md index 80b87713b7..71ff0ccbe3 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md @@ -22,7 +22,7 @@ shortTitle: Excluir arquivos É possível excluir um arquivo individual no repositório{% ifversion fpt or ghes or ghec %} ou um diretório inteiro, incluindo todos os arquivos no diretório{% endif %}. -If you try to delete a file{% ifversion fpt or ghes or ghec %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your personal account and help you send a pull request to the original repository after you commit your change. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". +Se você tentar excluir um arquivo{% ifversion fpt or ghes or ghec %} ou diretório{% endif %} em um repositório no qual você não tem permissões de gravação, faremos uma bifurcação do projeto para a sua conta pessoal e iremos ajudar você a enviar um pull request para o repositório original depois de fazer commit da sua alteração. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". Se o arquivo{% ifversion fpt or ghes or ghec %} ou diretório{% endif %} que você excluiu contém dados cnfidenciais, os dados ainda estarão disponíveis no histórico Git do repositório. Para remover completamente o arquivo de {% data variables.product.product_name %}, você deve remover o arquivo do histórico do seu repositório. Para obter mais informações, consulte "[Remover dados confidenciais do repositório](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md index ba7d6e1578..d5f8f16ba4 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md @@ -26,7 +26,7 @@ Além de alterar o local do arquivo, também é possível [atualizar o conteúdo **Dicas**: -- If you try to move a file in a repository that you don’t have access to, we'll fork the project to your personal account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. +- Se você tentar mover um arquivo em um repositório que não tem acesso, bifurcaremos o projeto para sua conta pessoal e ajudaremos você a enviar [uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) para o repositório original depois de fazer o commit da alteração. - Alguns arquivos, como imagens, exigem que você os mova com a linha de comando. Para obter mais informações, consulte "[Mover um arquivo para um novo local usando a linha de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)". - {% data reusables.repositories.protected-branches-block-web-edits-uploads %} diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/renaming-a-file.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/renaming-a-file.md index 06de46bcfe..7c289b364f 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-files/renaming-a-file.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/renaming-a-file.md @@ -25,7 +25,7 @@ Renomear um arquivo também dá a oportunidade de [transferir o arquivo para um **Dicas**: -- If you try to rename a file in a repository that you don’t have access to, we will fork the project to your personal account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. +- Se você tentar renomear um arquivo em um repositório ao qual não tem acesso, bifurcaremos o projeto para sua conta pessoal e ajudaremos você a enviar [um pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) para o repositório original depois que fizer o commit da alteração. - Os nomes de arquivos criados por meio da interface da web podem conter apenas caracteres alfanuméricos e hífens (`-`). Para usar outros caracteres, crie e faça commit dos arquivos localmente, depois faça push deles para o repositório. - Alguns arquivos, como imagens, exigem que a renomeação seja feita usando a linha de comando. Para obter mais informações, consulte "[Renomear um arquivo usando a linha de comando](/articles/renaming-a-file-using-the-command-line)". diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md index eddee54b26..b40da88e03 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md @@ -22,25 +22,25 @@ A navegação por código ajuda você a ler, navegar e compreender o código mos A navegação pelo código usa a biblioteca de código aberto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). As estratégias de linguagem e navegação a seguir são compatíveis: -| Linguagem | Search-based code navigation | Precise code navigation | -|:----------:|:----------------------------:|:-----------------------:| -| C# | ✅ | | -| CodeQL | ✅ | | -| Elixir | ✅ | | -| Go | ✅ | | -| Java | ✅ | | -| JavaScript | ✅ | | -| PHP | ✅ | | -| Python | ✅ | ✅ | -| Ruby | ✅ | | -| TypeScript | ✅ | | +| Linguagem | Navegação de código baseado em pesquisa | Navegação de código precisa | +|:----------:|:---------------------------------------:|:---------------------------:| +| C# | ✅ | | +| CodeQL | ✅ | | +| Elixir | ✅ | | +| Go | ✅ | | +| Java | ✅ | | +| JavaScript | ✅ | | +| PHP | ✅ | | +| Python | ✅ | ✅ | +| Ruby | ✅ | | +| TypeScript | ✅ | | Você não precisa configurar nada no seu repositório para habilitar a navegação do código. Nós iremos extrair automaticamente informações de navegação de código precisas e baseadas em pesquisa para essas linguagens compatíveis em todos os repositórios e você pode alternar entre as duas abordagens de navegação de código compatíveis se sua linguagem de programação for compatível com ambos. {% data variables.product.prodname_dotcom %} desenvolveu duas abordagens de código de navegação com base no código aberto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) e [`stack-graphs`](https://github.com/github/stack-graphs) library: - - Search-based - searches all definitions and references across a repository to find entities with a given name - - Precise - resolves definitions and references based on the set of classes, functions, and imported definitions at a given point in your code + - Baseado em pesquisa - Pesquisa todas as definições e referências em um repositório para encontrar entidades com um determinado nome + - Preciso - resolve definições e referências baseadas no conjunto de classes, funções, e definições importadas em um determinado ponto do seu código Para aprender mais sobre essas abordagens, consulte "[Navegação precisa e baseada em pesquisa](#precise-and-search-based-navigation)". diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/pt-BR/content/repositories/working-with-files/using-files/viewing-a-file.md index 9fa892acb4..7090d9d632 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/viewing-a-file.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/viewing-a-file.md @@ -50,10 +50,10 @@ Em um arquivo ou uma pull request, também é possível usar o menu {% octicon " {% if blame-ignore-revs %} -## Ignore commits in the blame view +## Ignorar commits na exibição do último responsável {% note %} -**Note:** Ignoring commits in the blame view is currently in public beta and subject to change. +**Observação:** Ignorar commits na visualização de último responsável encontra-se atualmente na versão beta pública e sujeita a alterações. {% endnote %} @@ -70,13 +70,13 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t 69d029cec8337c616552756310748c4a507bd75a ``` -3. Commit and push the changes. +3. Faça o commit e faça push das alterações. -Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden: +Agora, quando você visitar a visualização do último responsável, as revisões listadas não serão incluídas na visualização do último responsável. Você verá um banner **Ignoring revisions in .git-blame-ignore-revs** indicando que alguns commits podem ser ocultados: -![Screenshot of a banner on the blame view linking to the .git-blame-ignore-revs file](/assets/images/help/repository/blame-ignore-revs-file.png) +![Captura de tela de um banner na visualização dos últimos responsáveis vinculada ao arquivo .git-blame-ignore-revs](/assets/images/help/repository/blame-ignore-revs-file.png) -This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well: +Isso pode ser útil quando alguns commits fizerem amplas alterações no seu código. Você pode usar o arquivo ao executar `git blame` localmente: ```shell git blame --ignore-revs-file .git-blame-ignore-revs diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 67d9eb3782..870ce2e804 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -42,8 +42,8 @@ O {% data variables.product.product_name %} pode exibir diversos formatos comuns {% note %} **Observação:** -- {% data variables.product.prodname_dotcom %} does not support comparing the differences between PSD files. -- If you are using the Firefox browser, SVGs on {% data variables.product.prodname_dotcom %} may not render. +- {% data variables.product.prodname_dotcom %} não é compatível com a comparação de diferenças entre arquivos PSD. +- Se você estiver utilizando o navegador Firefox, os SVGs em {% data variables.product.prodname_dotcom %} não poderão ser interpretados. {% endnote %} @@ -308,7 +308,7 @@ Ainda pode ser possível renderizar os dados convertendo o arquivo `.geojson` em ### Leia mais -* [Leaflet.js documentation](https://leafletjs.com/) +* [Documentação do Leaflet.js](https://leafletjs.com/) * [Documentação MapBox marcadores de estilo](http://www.mapbox.com/developers/simplestyle/) * [Wiki TopoJSON](https://github.com/mbostock/topojson/wiki) diff --git a/translations/pt-BR/content/rest/actions/artifacts.md b/translations/pt-BR/content/rest/actions/artifacts.md index a7767ab769..0bc2e0d810 100644 --- a/translations/pt-BR/content/rest/actions/artifacts.md +++ b/translations/pt-BR/content/rest/actions/artifacts.md @@ -1,8 +1,8 @@ --- -title: GitHub Actions Artifacts +title: Artefatos do GitHub Actions allowTitleToDifferFromFilename: true shortTitle: Artefatos -intro: 'The {% data variables.product.prodname_actions %} Artifacts API allows you to download, delete, and retrieve information about workflow artifacts.' +intro: 'A API de Artefatos de {% data variables.product.prodname_actions %} permite que você faça o download, exclua e recupere informações sobre artefatos de fluxo de trabalho.' topics: - API versions: @@ -12,8 +12,8 @@ versions: ghec: '*' --- -## About the Artifacts API +## Sobre a API de Artefatos -The {% data variables.product.prodname_actions %} Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +A API de Artefatos de {% data variables.product.prodname_actions %} permite que você faça o download, exclua e recupere informações sobre artefatos de fluxo de trabalho. {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/pt-BR/content/rest/actions/cache.md b/translations/pt-BR/content/rest/actions/cache.md index 602bb70213..67e94c39ae 100644 --- a/translations/pt-BR/content/rest/actions/cache.md +++ b/translations/pt-BR/content/rest/actions/cache.md @@ -1,8 +1,8 @@ --- -title: GitHub Actions Cache +title: Cache do GitHub Actions allowTitleToDifferFromFilename: true shortTitle: Cache -intro: 'The {% data variables.product.prodname_actions %} Cache API allows you to query and manage the {% data variables.product.prodname_actions %} cache for repositories.' +intro: 'A API do cache do {% data variables.product.prodname_actions %} permite que você consulte e gerencie o cache {% data variables.product.prodname_actions %} para repositórios.' topics: - API versions: @@ -11,6 +11,6 @@ versions: ghes: '>3.4' --- -## About the Cache API +## About a API do cache -The {% data variables.product.prodname_actions %} Cache API allows you to query and manage the {% data variables.product.prodname_actions %} cache for repositories. Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy)". +A API do cache do {% data variables.product.prodname_actions %} permite que você consulte e gerencie o cache {% data variables.product.prodname_actions %} para repositórios. Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy)". diff --git a/translations/pt-BR/content/rest/actions/permissions.md b/translations/pt-BR/content/rest/actions/permissions.md index 671fdd3c71..671d3fd900 100644 --- a/translations/pt-BR/content/rest/actions/permissions.md +++ b/translations/pt-BR/content/rest/actions/permissions.md @@ -1,8 +1,8 @@ --- -title: GitHub Actions Permissions +title: Permissões do GitHub Actions allowTitleToDifferFromFilename: true shortTitle: Permissões -intro: 'The {% data variables.product.prodname_actions %} Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions{% if actions-workflow-policy %} and reusable workflows{% endif %} are allowed to run.' +intro: 'A API de Permissões do {% data variables.product.prodname_actions %} permite que você defina as permissões para o que empresas, organizações, e repositórios estão autorizados a executar {% data variables.product.prodname_actions %}, e quais ações{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} porem ser executados.' topics: - API versions: @@ -12,6 +12,6 @@ versions: ghec: '*' --- -## About the Permissions API +## Sobre a API de permissões -The {% data variables.product.prodname_actions %} Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions{% if actions-workflow-policy %} and reusable workflows{% endif %} are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %} +A API de Permissões do {% data variables.product.prodname_actions %} permite que você defina as permissões para o que empresas, organizações, e repositórios estão autorizados a executar {% data variables.product.prodname_actions %}, e quais ações{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} estão autorizados a ser executados.{% ifversion fpt or ghec or ghes %} Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)".{% endif %} diff --git a/translations/pt-BR/content/rest/actions/secrets.md b/translations/pt-BR/content/rest/actions/secrets.md index 1b4e065ddf..e771bbd3c3 100644 --- a/translations/pt-BR/content/rest/actions/secrets.md +++ b/translations/pt-BR/content/rest/actions/secrets.md @@ -1,8 +1,8 @@ --- -title: GitHub Actions Secrets +title: Segredos do GitHub Actions allowTitleToDifferFromFilename: true shortTitle: Segredos -intro: 'The {% data variables.product.prodname_actions %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets that can be used in {% data variables.product.prodname_actions %} workflows.' +intro: 'A API de Segredos {% data variables.product.prodname_actions %} permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados que podem ser usados nos fluxos de trabalho de {% data variables.product.prodname_actions %}.' topics: - API versions: @@ -12,8 +12,8 @@ versions: ghec: '*' --- -## About the Secrets API +## Sobre a API de segredos -The {% data variables.product.prodname_actions %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets that can be used in {% data variables.product.prodname_actions %} workflows. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +A API de Segredos {% data variables.product.prodname_actions %} permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados que podem ser usados nos fluxos de trabalho de {% data variables.product.prodname_actions %}. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão `segredos` para usar esta API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos. diff --git a/translations/pt-BR/content/rest/actions/self-hosted-runner-groups.md b/translations/pt-BR/content/rest/actions/self-hosted-runner-groups.md index 4b935c9df0..c859c33cd1 100644 --- a/translations/pt-BR/content/rest/actions/self-hosted-runner-groups.md +++ b/translations/pt-BR/content/rest/actions/self-hosted-runner-groups.md @@ -11,8 +11,8 @@ versions: --- -## About the Self-hosted runner groups API +## Sobre a API de grupos de executores auto-hospedados -The Self-hosted runners groups API allows you manage groups of self-hosted runners. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". +A API de grupos de executores auto-hospedados permite que você gerencie grupos de executores auto-hospedados. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Os usuários autenticados devem ter acesso de administrador a repositórios ou organizações ou ao escopo `manage_runners:corporativo` para que as empresas usem esta API. diff --git a/translations/pt-BR/content/rest/actions/self-hosted-runners.md b/translations/pt-BR/content/rest/actions/self-hosted-runners.md index f63312550f..9e7173cb83 100644 --- a/translations/pt-BR/content/rest/actions/self-hosted-runners.md +++ b/translations/pt-BR/content/rest/actions/self-hosted-runners.md @@ -1,6 +1,6 @@ --- title: Executores auto-hospedados -intro: 'The Self-hosted runners API allows you to register, view, and delete self-hosted runners.' +intro: 'A API de executores auto-hospedados permite que você registre, visualize e exclua executores auto-hospedados.' topics: - API versions: @@ -11,8 +11,8 @@ versions: --- -## About the Self-hosted runners API +## Sobre a API de executores auto-hospedados -The Self-hosted runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)". +A API de executores auto-hospedados permite que você registre, visualize e exclua executores auto-hospedados. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)". {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Os usuários autenticados devem ter acesso de administrador a repositórios ou organizações ou ao escopo `manage_runners:corporativo` para que as empresas usem esta API. diff --git a/translations/pt-BR/content/rest/actions/workflow-jobs.md b/translations/pt-BR/content/rest/actions/workflow-jobs.md index 371a754237..aeff95dfed 100644 --- a/translations/pt-BR/content/rest/actions/workflow-jobs.md +++ b/translations/pt-BR/content/rest/actions/workflow-jobs.md @@ -10,8 +10,8 @@ versions: ghec: '*' --- -## About the Workflow jobs API +## Sobre a API de trabalhos de fluxo de trabalho -The Workflow jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". +A API de Trabalhos de Fluxo de Trabalho permite que você visualize logs e trabalhos de fluxo de trabalho. {% data reusables.actions.about-workflow-jobs %} Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/pt-BR/content/rest/actions/workflow-runs.md b/translations/pt-BR/content/rest/actions/workflow-runs.md index 1e01fbc59a..fa1ef14aac 100644 --- a/translations/pt-BR/content/rest/actions/workflow-runs.md +++ b/translations/pt-BR/content/rest/actions/workflow-runs.md @@ -1,6 +1,6 @@ --- title: Execução de fluxo de trabalho -intro: 'The Workflow runs API allows you to view, re-run, cancel, and view logs for workflow runs.' +intro: 'A API de execução do Fluxo de trabalho permite que você visualize, execute novamente, cancele e visualize logs para execuções de fluxo de trabalho.' topics: - API versions: @@ -10,8 +10,8 @@ versions: ghec: '*' --- -## About the Workflow runs API +## Sobre a API de execuções de fluxo de trabalho -The Workflow runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} Para obter mais informações, consulte "[Gerenciando uma execução de fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". +A API de execução do Fluxo de trabalho permite que você visualize, execute novamente, cancele e visualize logs para execuções de fluxo de trabalho. {% data reusables.actions.about-workflow-runs %} Para obter mais informações, consulte "[Gerenciando uma execução de fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/pt-BR/content/rest/actions/workflows.md b/translations/pt-BR/content/rest/actions/workflows.md index 0f88232eee..2c025bb3c5 100644 --- a/translations/pt-BR/content/rest/actions/workflows.md +++ b/translations/pt-BR/content/rest/actions/workflows.md @@ -10,7 +10,7 @@ versions: ghec: '*' --- -## About the Workflows API +## Sobre a API de fluxos de trabalho A API de fluxos de trabalho permite que você veja fluxos de trabalho para um repositório. {% data reusables.actions.about-workflows %} Para obter mais informações, consulte "[Automatizando seu fluxo de trabalho com o GitHub Actions](/actions/automating-your-workflow-with-github-actions)". diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml index 0973ff2246..36603a7d58 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -122,7 +122,7 @@ sections: heading: Re-run failed or individual GitHub Actions jobs notes: - | - You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/managing-workflow-runs/re-running-workflows-and-jobs)." + You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - heading: Dependency graph supports GitHub Actions notes: @@ -313,7 +313,7 @@ sections: - | GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories)." + New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." - | Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." - | diff --git a/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml index 1db9dda802..c38864dab6 100644 --- a/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml +++ b/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -23,14 +23,14 @@ sections: - | GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - heading: 'Gráfico de dependências' notes: - | - Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." - heading: 'Alertas do Dependabot' notes: @@ -76,7 +76,7 @@ sections: heading: 'Audit log accessible via REST API' notes: - | - You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." - heading: 'Expiration dates for personal access tokens' notes: @@ -134,7 +134,7 @@ sections: heading: 'GitHub Actions' notes: - | - To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." - | The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. @@ -175,7 +175,7 @@ sections: heading: 'Repositórios' notes: - | - GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - | You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. - diff --git a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md index bf2beb6d67..c6c4e41402 100644 --- a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md +++ b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ Os membros com permissões de mantenedor da equipe podem: - [Adicionar integrantes da organização à equipe](/articles/adding-organization-members-to-a-team) - [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team) - [Promover um membro da equipe existente para um mantenedor de equipe](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- Remove the team's access to repositories +- Removea o acesso da equipe aos repositórios - [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 6b10663dfe..d391247e97 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -80,6 +80,7 @@ For the overall list of included tools for each runner operating system, see the * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) +* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md) * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index f4819b9441..54025d7284 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -19,7 +19,9 @@ topics: {% ifversion ghec %} -{% data variables.product.product_name %} 上的企业所有者可以控制身份验证和访问企业资源的要求。 您可以选择允许成员创建和管理用户帐户，或者您的企业可以为成员创建和管理帐户。 如果您允许成员管理自己的帐户，则还可以配置 SAML 身份验证，以提高安全性，并集中团队使用的 Web 应用程序的身份和访问权限。 如果选择管理成员的用户帐户，则必须配置 SAML 身份验证。 +{% data variables.product.product_name %} 上的企业所有者可以控制身份验证和访问企业资源的要求。 + +You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. 如果您允许成员管理自己的帐户，则还可以配置 SAML 身份验证，以提高安全性，并集中团队使用的 Web 应用程序的身份和访问权限。 如果选择管理成员的用户帐户，则必须配置 SAML 身份验证。 ## {% data variables.product.product_name %} 的身份验证方法 diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md index ae2d06af75..7bafef913e 100644 --- a/translations/zh-CN/content/admin/index.md +++ b/translations/zh-CN/content/admin/index.md @@ -71,13 +71,13 @@ changelog: featuredLinks: guides: - '{% ifversion ghae %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}' + - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise + - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies - '{% ifversion ghae %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}' - '{% ifversion ghes %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}' - '{% ifversion ghes %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}' - '{% ifversion ghes %}/admin/overview/about-upgrades-to-new-releases{% endif %}' - '{% ifversion ghec %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise{% endif %}' - - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users{% endif %}' - - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise{% endif %}' - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise{% endif %}' - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise guideCards: diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md index 14571af933..6ebe6cb0fe 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -32,18 +32,18 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ {% endif %} -Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion ghec %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %} +Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." + +{% ifversion ghec %} +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +{% endif %} + +Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." {% ifversion ghec %} -Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for your enterprise](/admin/policies)." - {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -{% elsif ghes or ghae %} - -For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)." - {% endif %} ## About administration of your enterprise account diff --git a/translations/zh-CN/content/admin/overview/creating-an-enterprise-account.md b/translations/zh-CN/content/admin/overview/creating-an-enterprise-account.md index 635ac8a067..c5c9fa711c 100644 --- a/translations/zh-CN/content/admin/overview/creating-an-enterprise-account.md +++ b/translations/zh-CN/content/admin/overview/creating-an-enterprise-account.md @@ -16,7 +16,7 @@ shortTitle: Create enterprise account {% data variables.product.prodname_ghe_cloud %} includes the option to create an enterprise account, which enables collaboration between multiple organizations and gives administrators a single point of visibility and management. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." -{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to move to invoicing. +{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you. An enterprise account is included in {% data variables.product.prodname_ghe_cloud %}, so creating one will not affect your bill. @@ -29,7 +29,10 @@ If the organization is connected to {% data variables.product.prodname_ghe_serve ## Creating an enterprise account on {% data variables.product.prodname_dotcom %} -To create an enterprise account on {% data variables.product.prodname_dotcom %}, your organization must be using {% data variables.product.prodname_ghe_cloud %} and paying by invoice. +To create an enterprise account, your organization must be using {% data variables.product.prodname_ghe_cloud %}. + +If you pay by invoice, you can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. If you do not currently pay by invoice, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you. + {% data reusables.organizations.billing-settings %} 1. Click **Upgrade to enterprise account**. diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md new file mode 100644 index 0000000000..7f7eb349db --- /dev/null +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md @@ -0,0 +1,30 @@ +--- +title: About enterprise policies +intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.' +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - Enterprise + - Policies +--- + +To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. + +{% data reusables.enterprise.about-policies %} + +For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise. + +By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." + +While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise. + +{% ifversion ghes %} +Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)." +{% endif %} + +## 延伸阅读 + +- “[关于企业帐户](/admin/overview/about-enterprise-accounts)” diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index bf49e5cc0b..7a4b842e57 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -13,6 +13,7 @@ topics: - Enterprise - Policies children: + - /about-enterprise-policies - /enforcing-repository-management-policies-in-your-enterprise - /enforcing-team-policies-in-your-enterprise - /enforcing-project-board-policies-in-your-enterprise diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index df96487115..ef0ea220af 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -53,7 +53,7 @@ Each user on {% data variables.product.product_location %} consumes a seat on yo {% endif %} -{% data reusables.billing.about-invoices-for-enterprises %} For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} {%- ifversion ghes %} - "[About per-user pricing](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)" diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index aa3e5d243c..e9eea5a2f7 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -17,7 +17,7 @@ shortTitle: View subscription & usage ## About billing for enterprise accounts -You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %} diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 517f94bf5d..2580027b6f 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1481,6 +1481,17 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS - {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. +### Webhook payload object + +| Key | Type | Description | +|-----|-----|-----| +| `inputs` | `object` | Inputs to the workflow. Each key represents the name of the input while it's value represents the value of that input. | +{% data reusables.webhooks.org_desc %} +| `ref` | `string` | The branch ref from which the workflow was run. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.sender_desc %} +| `workflow` | `string` | Relative path to the workflow file which contains the workflow. | + ### Webhook payload example {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 109eb89028..7935a24b28 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -56,21 +56,23 @@ Your organization's billing settings page allows you to manage settings like you Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." ### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} - {% note %} - -To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). - - {% endnote %} #### 1. About enterprise accounts An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." -#### 2. Adding organizations to your enterprise account + +#### 2. Creating an enterpise account + + {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." + + {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you. + +#### 3. Adding organizations to your enterprise account You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. -#### 3. Viewing the subscription and usage for your enterprise account +#### 4. Viewing the subscription and usage for your enterprise account You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." ## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} diff --git a/translations/zh-CN/data/learning-tracks/admin.yml b/translations/zh-CN/data/learning-tracks/admin.yml index 6ef7226986..a7aa266e92 100644 --- a/translations/zh-CN/data/learning-tracks/admin.yml +++ b/translations/zh-CN/data/learning-tracks/admin.yml @@ -135,5 +135,4 @@ get_started_with_your_enterprise_account: - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise - - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise - - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise + - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies diff --git a/translations/zh-CN/data/reusables/enterprise/about-policies.md b/translations/zh-CN/data/reusables/enterprise/about-policies.md new file mode 100644 index 0000000000..7fd5303231 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise/about-policies.md @@ -0,0 +1 @@ +Each enterprise policy controls the options available for a policy at the organization level. You can choose to not enforce a policy, which allows organization owners to configure the policy for the organization, or you can choose from a set of options to enforce for all organizations owned by your enterprise. \ No newline at end of file diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index b65e461e72..57f3433ef9 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -36,6 +36,7 @@ search: homepage: explore_by_product: 按产品浏览 version_picker: 版本 + description: Help for wherever you are on your GitHub journey. toc: getting_started: 入门指南 popular: 热门