Merge pull request #22037 from github/repo-sync

repo sync

components/release-notes/GHAEReleaseNotes.tsx

@@ -18,12 +18,10 @@ export function GHAEReleaseNotes({ context }: GitHubAEProps) {
     <div className="d-flex">
       <article className="min-width-0 flex-1">
         <div className="d-flex flex-items-center flex-justify-between color-bg-default px-5 py-2">
-          <div></div>
           <h1 className="f4 py-3 m-0">{currentVersion.planTitle} release notes</h1>
-          <div></div>
         </div>
 
-        <MarkdownContent data-search="article-content">
+        <MarkdownContent data-search="article-body">
           {releaseNotes.map((patch) => {
             return (
               <GHAEReleaseNotePatch
@@ -44,7 +42,7 @@ export function GHAEReleaseNotes({ context }: GitHubAEProps) {
         )}
       >
         <nav className="height-full overflow-auto">
-          <MarkdownContent data-search="article-content">
+          <MarkdownContent>
             <ul className="list-style-none pl-0 text-bold">
               {releases.map((release) => {
                 return (

components/release-notes/GHESReleaseNotes.tsx

@@ -30,7 +30,7 @@ export function GHESReleaseNotes({ context }: Props) {
             {currentVersion.planTitle} {currentVersion.currentRelease} release notes
           </h1>
         </div>
-        <MarkdownContent data-search="article-content">
+        <MarkdownContent data-search="article-body">
           {releaseNotes.map((patch) => {
             return (
               <GHESReleaseNotePatch
@@ -56,7 +56,7 @@ export function GHESReleaseNotes({ context }: Props) {
         )}
       >
         <nav className="height-full overflow-auto">
-          <MarkdownContent data-search="article-content">
+          <MarkdownContent>
             <ul className="list-style-none pl-0 text-bold">
               {releases.map((release) => {
                 const releaseLink = `/${router.locale}/${currentVersion.plan}@${release.version}/${currentProduct?.id}/release-notes`

data/features/actions-stable-actor-ids.yml

@@ -4,4 +4,4 @@ versions:
   fpt: '*'
   ghec: '*'
   ghes: '>=3.7'
-  ghae: '>= 3.8'
+  ghae: '>=3.7'

data/features/autolink-reference-alphanumeric.yml

@@ -4,4 +4,4 @@ versions:
   fpt: '*'
   ghec: '*'
   ghes: '>=3.7'
-  ghae: '>= 3.8'
+  ghae: '>=3.7'

data/features/custom-pattern-dry-run-ga.yml

@@ -2,4 +2,4 @@
 versions:
   ghec: '*'
   ghes: '>3.6'
-  ghae: '>= 3.8'
+  ghae: '>3.6'

data/features/default-merge-squash-commit-message.yml

@@ -4,4 +4,4 @@ versions:
   fpt: '*'
   ghec: '*'
   ghes: '>=3.7'
-  ghae: '>= 3.8'
+  ghae: '>=3.7'

data/features/ssh-commit-verification.yml

@@ -5,4 +5,4 @@ versions:
   fpt: '*'
   ghec: '*'
   ghes: '>= 3.7'
-  ghae: '*'
+  ghae: '>= 3.7'

data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml

@@ -271,3 +271,11 @@ upcoming_changes:
     date: '2023-04-01T00:00:00+00:00'
     criticality: breaking
     owner: traumverloren
+  - location: Repository.squashPrTitleUsedAsDefault
+    description:
+      '`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle`
+      instead.'
+    reason: '`squashPrTitleUsedAsDefault` will be removed.'
+    date: '2023-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: github/pull_requests

data/graphql/ghae/schema.docs-ghae.graphql

@@ -33480,6 +33480,9 @@ type Repository implements Node & ProjectOwner & RepositoryInfo & Starrable & Su
   Whether a squash merge commit can use the pull request title as default.
   """
   squashPrTitleUsedAsDefault: Boolean!
+    @deprecated(
+      reason: "`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle` instead. Removal on 2023-04-01 UTC."
+    )
 
   """
   The SSH URL to clone this repository

data/graphql/ghec/graphql_upcoming_changes.public.yml

@@ -1762,3 +1762,11 @@ upcoming_changes:
     date: '2023-04-01T00:00:00+00:00'
     criticality: breaking
     owner: traumverloren
+  - location: Repository.squashPrTitleUsedAsDefault
+    description:
+      '`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle`
+      instead.'
+    reason: '`squashPrTitleUsedAsDefault` will be removed.'
+    date: '2023-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: github/pull_requests

data/graphql/ghec/schema.docs.graphql

@@ -6997,6 +6997,11 @@ input CreateProjectV2Input {
   """
   repositoryId: ID @possibleTypes(concreteTypes: ["Repository"])
 
+  """
+  The team to link the project to. The team will be granted read permissions.
+  """
+  teamId: ID @possibleTypes(concreteTypes: ["Team"])
+
   """
   The title of the project.
   """
@@ -41396,6 +41401,9 @@ type Repository implements Node & PackageOwner & ProjectOwner & ProjectV2Recent
   Whether a squash merge commit can use the pull request title as default.
   """
   squashPrTitleUsedAsDefault: Boolean!
+    @deprecated(
+      reason: "`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle` instead. Removal on 2023-04-01 UTC."
+    )
 
   """
   The SSH URL to clone this repository
@@ -45407,6 +45415,13 @@ type SponsorsListing implements Node {
   """
   activeGoal: SponsorsGoal
 
+  """
+  The name of the country or region with the maintainer's bank account or fiscal
+  host. Will only return a value when queried by the maintainer themselves, or
+  by an admin of the sponsorable organization.
+  """
+  billingCountryOrRegion: String
+
   """
   Identifies the date and time when the object was created.
   """
@@ -45448,6 +45463,13 @@ type SponsorsListing implements Node {
   """
   nextPayoutDate: Date
 
+  """
+  The name of the country or region where the maintainer resides. Will only
+  return a value when queried by the maintainer themselves, or by an admin of
+  the sponsorable organization.
+  """
+  residenceCountryOrRegion: String
+
   """
   The HTTP path for this Sponsors listing.
   """

data/graphql/graphql_upcoming_changes.public.yml

@@ -1762,3 +1762,11 @@ upcoming_changes:
     date: '2023-04-01T00:00:00+00:00'
     criticality: breaking
     owner: traumverloren
+  - location: Repository.squashPrTitleUsedAsDefault
+    description:
+      '`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle`
+      instead.'
+    reason: '`squashPrTitleUsedAsDefault` will be removed.'
+    date: '2023-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: github/pull_requests

data/graphql/schema.docs.graphql

@@ -6997,6 +6997,11 @@ input CreateProjectV2Input {
   """
   repositoryId: ID @possibleTypes(concreteTypes: ["Repository"])
 
+  """
+  The team to link the project to. The team will be granted read permissions.
+  """
+  teamId: ID @possibleTypes(concreteTypes: ["Team"])
+
   """
   The title of the project.
   """
@@ -41396,6 +41401,9 @@ type Repository implements Node & PackageOwner & ProjectOwner & ProjectV2Recent
   Whether a squash merge commit can use the pull request title as default.
   """
   squashPrTitleUsedAsDefault: Boolean!
+    @deprecated(
+      reason: "`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle` instead. Removal on 2023-04-01 UTC."
+    )
 
   """
   The SSH URL to clone this repository
@@ -45407,6 +45415,13 @@ type SponsorsListing implements Node {
   """
   activeGoal: SponsorsGoal
 
+  """
+  The name of the country or region with the maintainer's bank account or fiscal
+  host. Will only return a value when queried by the maintainer themselves, or
+  by an admin of the sponsorable organization.
+  """
+  billingCountryOrRegion: String
+
   """
   Identifies the date and time when the object was created.
   """
@@ -45448,6 +45463,13 @@ type SponsorsListing implements Node {
   """
   nextPayoutDate: Date
 
+  """
+  The name of the country or region where the maintainer resides. Will only
+  return a value when queried by the maintainer themselves, or by an admin of
+  the sponsorable organization.
+  """
+  residenceCountryOrRegion: String
+
   """
   The HTTP path for this Sponsors listing.
   """

lib/graphql/static/changelog.json

@@ -1,4 +1,26 @@
 [
+  {
+    "schemaChanges": [
+      {
+        "title": "The GraphQL schema includes these changes:",
+        "changes": [
+          "<p>Input field <code>teamId</code> was added to input object type 'CreateProjectV2Input'</p>",
+          "<p>Field <code>billingCountryOrRegion</code> was added to object type <code>SponsorsListing</code></p>",
+          "<p>Field <code>residenceCountryOrRegion</code> was added to object type <code>SponsorsListing</code></p>"
+        ]
+      }
+    ],
+    "previewChanges": [],
+    "upcomingChanges": [
+      {
+        "title": "The following changes will be made to the schema:",
+        "changes": [
+          "<p>On member <code>Repository.squashPrTitleUsedAsDefault</code>:<code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead. <strong>Effective 2023-04-01</strong>.</p>"
+        ]
+      }
+    ],
+    "date": "2022-11-15"
+  },
   {
     "schemaChanges": [
       {

lib/graphql/static/schema-dotcom.json

@@ -58189,7 +58189,9 @@
           "type": "Boolean!",
           "id": "boolean",
           "kind": "scalars",
-          "href": "/graphql/reference/scalars#boolean"
+          "href": "/graphql/reference/scalars#boolean",
+          "isDeprecated": true,
+          "deprecationReason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead. Removal on 2023-04-01 UTC.</p>"
         },
         {
           "name": "sshUrl",
@@ -61707,6 +61709,14 @@
           "kind": "objects",
           "href": "/graphql/reference/objects#sponsorsgoal"
         },
+        {
+          "name": "billingCountryOrRegion",
+          "description": "<p>The name of the country or region with the maintainer's bank account or fiscal\nhost. Will only return a value when queried by the maintainer themselves, or\nby an admin of the sponsorable organization.</p>",
+          "type": "String",
+          "id": "string",
+          "kind": "scalars",
+          "href": "/graphql/reference/scalars#string"
+        },
         {
           "name": "createdAt",
           "description": "<p>Identifies the date and time when the object was created.</p>",
@@ -61771,6 +61781,14 @@
           "kind": "scalars",
           "href": "/graphql/reference/scalars#date"
         },
+        {
+          "name": "residenceCountryOrRegion",
+          "description": "<p>The name of the country or region where the maintainer resides. Will only\nreturn a value when queried by the maintainer themselves, or by an admin of\nthe sponsorable organization.</p>",
+          "type": "String",
+          "id": "string",
+          "kind": "scalars",
+          "href": "/graphql/reference/scalars#string"
+        },
         {
           "name": "resourcePath",
           "description": "<p>The HTTP path for this Sponsors listing.</p>",
@@ -84745,6 +84763,15 @@
           "href": "/graphql/reference/scalars#id",
           "isDeprecated": false
         },
+        {
+          "name": "teamId",
+          "description": "<p>The team to link the project to. The team will be granted read permissions.</p>",
+          "type": "ID",
+          "id": "id",
+          "kind": "scalars",
+          "href": "/graphql/reference/scalars#id",
+          "isDeprecated": false
+        },
         {
           "name": "title",
           "description": "<p>The title of the project.</p>",

lib/graphql/static/schema-ghae.json

@@ -47438,7 +47438,9 @@
           "type": "Boolean!",
           "id": "boolean",
           "kind": "scalars",
-          "href": "/graphql/reference/scalars#boolean"
+          "href": "/graphql/reference/scalars#boolean",
+          "isDeprecated": true,
+          "deprecationReason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead. Removal on 2023-04-01 UTC.</p>"
         },
         {
           "name": "sshUrl",

lib/graphql/static/schema-ghec.json

@@ -58189,7 +58189,9 @@
           "type": "Boolean!",
           "id": "boolean",
           "kind": "scalars",
-          "href": "/graphql/reference/scalars#boolean"
+          "href": "/graphql/reference/scalars#boolean",
+          "isDeprecated": true,
+          "deprecationReason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead. Removal on 2023-04-01 UTC.</p>"
         },
         {
           "name": "sshUrl",
@@ -61707,6 +61709,14 @@
           "kind": "objects",
           "href": "/graphql/reference/objects#sponsorsgoal"
         },
+        {
+          "name": "billingCountryOrRegion",
+          "description": "<p>The name of the country or region with the maintainer's bank account or fiscal\nhost. Will only return a value when queried by the maintainer themselves, or\nby an admin of the sponsorable organization.</p>",
+          "type": "String",
+          "id": "string",
+          "kind": "scalars",
+          "href": "/graphql/reference/scalars#string"
+        },
         {
           "name": "createdAt",
           "description": "<p>Identifies the date and time when the object was created.</p>",
@@ -61771,6 +61781,14 @@
           "kind": "scalars",
           "href": "/graphql/reference/scalars#date"
         },
+        {
+          "name": "residenceCountryOrRegion",
+          "description": "<p>The name of the country or region where the maintainer resides. Will only\nreturn a value when queried by the maintainer themselves, or by an admin of\nthe sponsorable organization.</p>",
+          "type": "String",
+          "id": "string",
+          "kind": "scalars",
+          "href": "/graphql/reference/scalars#string"
+        },
         {
           "name": "resourcePath",
           "description": "<p>The HTTP path for this Sponsors listing.</p>",
@@ -84745,6 +84763,15 @@
           "href": "/graphql/reference/scalars#id",
           "isDeprecated": false
         },
+        {
+          "name": "teamId",
+          "description": "<p>The team to link the project to. The team will be granted read permissions.</p>",
+          "type": "ID",
+          "id": "id",
+          "kind": "scalars",
+          "href": "/graphql/reference/scalars#id",
+          "isDeprecated": false
+        },
         {
           "name": "title",
           "description": "<p>The title of the project.</p>",

lib/graphql/static/upcoming-changes.json

@@ -1,6 +1,14 @@
 {
   "dotcom": {
     "2023-04-01": [
+      {
+        "location": "Repository.squashPrTitleUsedAsDefault",
+        "description": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead.</p>",
+        "reason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed.</p>",
+        "date": "2023-04-01",
+        "criticality": "breaking",
+        "owner": "github/pull_requests"
+      },
       {
         "location": "ProjectV2View.verticalGroupBy",
         "description": "<p><code>verticalGroupBy</code> will be removed. Check out the <code>ProjectV2View#vertical_group_by_fields</code> API as an example for the more capable alternative.</p>",
@@ -1467,6 +1475,14 @@
   },
   "ghec": {
     "2023-04-01": [
+      {
+        "location": "Repository.squashPrTitleUsedAsDefault",
+        "description": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead.</p>",
+        "reason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed.</p>",
+        "date": "2023-04-01",
+        "criticality": "breaking",
+        "owner": "github/pull_requests"
+      },
       {
         "location": "ProjectV2View.verticalGroupBy",
         "description": "<p><code>verticalGroupBy</code> will be removed. Check out the <code>ProjectV2View#vertical_group_by_fields</code> API as an example for the more capable alternative.</p>",
@@ -3729,6 +3745,14 @@
   },
   "ghae": {
     "2023-04-01": [
+      {
+        "location": "Repository.squashPrTitleUsedAsDefault",
+        "description": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead.</p>",
+        "reason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed.</p>",
+        "date": "2023-04-01",
+        "criticality": "breaking",
+        "owner": "github/pull_requests"
+      },
       {
         "location": "ProjectV2View.verticalGroupBy",
         "description": "<p><code>verticalGroupBy</code> will be removed. Check out the <code>ProjectV2View#vertical_group_by_fields</code> API as an example for the more capable alternative.</p>",

translations/log/msft-cn-resets.csv

@@ -484,6 +484,7 @@ translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-
 translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
 translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
 translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
+translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,broken liquid tags
 translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
 translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
 translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
@@ -506,24 +507,21 @@ translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and
 translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,rendering error
 translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md,rendering error
 translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
-translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
+translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
 translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
 translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
 translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
 translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
@@ -578,13 +576,10 @@ translations/zh-CN/content/admin/identity-and-access-management/using-built-in-a
 translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
 translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,rendering error
@@ -694,7 +689,6 @@ translations/zh-CN/content/code-security/adopting-github-advanced-security-at-sc
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
@@ -704,13 +698,11 @@ translations/zh-CN/content/code-security/code-scanning/automatically-scanning-yo
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -738,6 +730,7 @@ translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-se
 translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error
 translations/zh-CN/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
 translations/zh-CN/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
+translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
 translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md,rendering error
 translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
 translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
@@ -782,7 +775,6 @@ translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypte
 translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
-translations/zh-CN/content/codespaces/overview.md,broken liquid tags
 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,broken liquid tags
 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
@@ -794,7 +786,6 @@ translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/set
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags
-translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags
 translations/zh-CN/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags
 translations/zh-CN/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags
 translations/zh-CN/content/codespaces/troubleshooting/index.md,broken liquid tags
@@ -806,12 +797,12 @@ translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-g
 translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
 translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
 translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
+translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md,broken liquid tags
 translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
 translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
 translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
 translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
 translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
-translations/zh-CN/content/copilot/overview-of-github-copilot/about-github-copilot.md,broken liquid tags
 translations/zh-CN/content/copilot/quickstart.md,broken liquid tags
 translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
 translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
@@ -840,6 +831,7 @@ translations/zh-CN/content/discussions/collaborating-with-your-community-using-d
 translations/zh-CN/content/discussions/guides/finding-your-discussions.md,broken liquid tags
 translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
 translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags
+translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,broken liquid tags
 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags
 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags
 translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
@@ -876,8 +868,7 @@ translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md,re
 translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid tags
 translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error
 translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
-translations/zh-CN/content/get-started/quickstart/github-glossary.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
+translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
 translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
 translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
 translations/zh-CN/content/get-started/using-git/about-git-rebase.md,broken liquid tags
@@ -888,7 +879,6 @@ translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,render
 translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
 translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
 translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md,rendering error
-translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags
 translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
 translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error
 translations/zh-CN/content/github-cli/github-cli/quickstart.md,rendering error
@@ -924,7 +914,6 @@ translations/zh-CN/content/organizations/managing-organization-settings/managing
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
-translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
 translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
@@ -1006,7 +995,6 @@ translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags
 translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags
 translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags
 translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags
-translations/zh-CN/content/rest/dependency-graph/dependency-review.md,broken liquid tags
 translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
 translations/zh-CN/content/rest/enterprise-admin/announcement.md,broken liquid tags
 translations/zh-CN/content/rest/enterprise-admin/billing.md,broken liquid tags
@@ -1083,6 +1071,8 @@ translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs
 translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md,rendering error
 translations/zh-CN/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
+translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/private-repository-forks-options.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/ref_name-description.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
 translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
@@ -1113,13 +1103,10 @@ translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
 translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
 translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
 translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
-translations/zh-CN/data/reusables/code-scanning/codeql-runner-analyze-example.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
-translations/zh-CN/data/reusables/code-scanning/edit-workflow.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags
@@ -1181,7 +1168,6 @@ translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-
 translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
 translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/copilot.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
 translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,rendering error
 translations/zh-CN/data/reusables/gated-features/secret-scanning.md,rendering error

translations/log/msft-pt-resets.csv

@@ -489,6 +489,7 @@ translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-
 translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
 translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
 translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
+translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,broken liquid tags
 translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
 translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
 translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
@@ -511,24 +512,21 @@ translations/pt-BR/content/actions/using-workflows/sharing-workflows-secrets-and
 translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,rendering error
 translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md,rendering error
 translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
-translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
+translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
 translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
 translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
 translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
-translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
 translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
-translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
 translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
@@ -583,13 +581,10 @@ translations/pt-BR/content/admin/identity-and-access-management/using-built-in-a
 translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
-translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,broken liquid tags
-translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
-translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
 translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags
@@ -698,7 +693,6 @@ translations/pt-BR/content/code-security/adopting-github-advanced-security-at-sc
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
@@ -708,13 +702,11 @@ translations/pt-BR/content/code-security/code-scanning/automatically-scanning-yo
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
-translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -742,6 +734,7 @@ translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-se
 translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error
 translations/pt-BR/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
 translations/pt-BR/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
+translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
 translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md,rendering error
 translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
 translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
@@ -786,11 +779,9 @@ translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypte
 translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
-translations/pt-BR/content/codespaces/overview.md,broken liquid tags
 translations/pt-BR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,broken liquid tags
 translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
 translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
-translations/pt-BR/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags
@@ -798,7 +789,6 @@ translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/set
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags
-translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags
 translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags
 translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags
 translations/pt-BR/content/codespaces/troubleshooting/index.md,broken liquid tags
@@ -810,12 +800,12 @@ translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-g
 translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
 translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
 translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
+translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md,broken liquid tags
 translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
 translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
 translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
 translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
 translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
-translations/pt-BR/content/copilot/overview-of-github-copilot/about-github-copilot.md,broken liquid tags
 translations/pt-BR/content/copilot/quickstart.md,broken liquid tags
 translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
 translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
@@ -843,6 +833,7 @@ translations/pt-BR/content/discussions/collaborating-with-your-community-using-d
 translations/pt-BR/content/discussions/guides/finding-your-discussions.md,broken liquid tags
 translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
 translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags
+translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,broken liquid tags
 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags
 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags
 translations/pt-BR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
@@ -879,8 +870,7 @@ translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md,re
 translations/pt-BR/content/get-started/quickstart/create-a-repo.md,broken liquid tags
 translations/pt-BR/content/get-started/quickstart/fork-a-repo.md,rendering error
 translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
-translations/pt-BR/content/get-started/quickstart/github-glossary.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
+translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
 translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
 translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
 translations/pt-BR/content/get-started/using-git/about-git-rebase.md,broken liquid tags
@@ -891,7 +881,6 @@ translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md,render
 translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
 translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
 translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md,rendering error
-translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags
 translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
 translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error
 translations/pt-BR/content/github-cli/github-cli/quickstart.md,rendering error
@@ -927,7 +916,6 @@ translations/pt-BR/content/organizations/managing-organization-settings/managing
 translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
 translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
-translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md,broken liquid tags
 translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
 translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
 translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
@@ -1009,7 +997,6 @@ translations/pt-BR/content/rest/activity/notifications.md,broken liquid tags
 translations/pt-BR/content/rest/apps/oauth-applications.md,broken liquid tags
 translations/pt-BR/content/rest/codespaces/codespaces.md,broken liquid tags
 translations/pt-BR/content/rest/dependabot/index.md,broken liquid tags
-translations/pt-BR/content/rest/dependency-graph/dependency-review.md,broken liquid tags
 translations/pt-BR/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
 translations/pt-BR/content/rest/enterprise-admin/announcement.md,broken liquid tags
 translations/pt-BR/content/rest/enterprise-admin/billing.md,broken liquid tags
@@ -1092,6 +1079,8 @@ translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs
 translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
 translations/pt-BR/data/reusables/actions/more-resources-for-ghes.md,rendering error
 translations/pt-BR/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
+translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md,broken liquid tags
+translations/pt-BR/data/reusables/actions/private-repository-forks-options.md,broken liquid tags
 translations/pt-BR/data/reusables/actions/ref_name-description.md,broken liquid tags
 translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
 translations/pt-BR/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
@@ -1122,13 +1111,10 @@ translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
 translations/pt-BR/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
 translations/pt-BR/data/reusables/classroom/about-autograding.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags
-translations/pt-BR/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
 translations/pt-BR/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
-translations/pt-BR/data/reusables/code-scanning/codeql-runner-analyze-example.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
-translations/pt-BR/data/reusables/code-scanning/edit-workflow.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/licensing-note.md,broken liquid tags
@@ -1189,7 +1175,6 @@ translations/pt-BR/data/reusables/enterprise_user_management/consider-usernames-
 translations/pt-BR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
 translations/pt-BR/data/reusables/files/choose-commit-email.md,broken liquid tags
 translations/pt-BR/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
-translations/pt-BR/data/reusables/gated-features/copilot.md,broken liquid tags
 translations/pt-BR/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
 translations/pt-BR/data/reusables/gated-features/secret-scanning-partner.md,rendering error
 translations/pt-BR/data/reusables/gated-features/secret-scanning.md,rendering error

translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md

@@ -1,31 +1,20 @@
 ---
-title: Aprovando execuções de fluxo de trabalho das bifurcações públicas
-intro: 'Quando um colaborador externo envia um pull request para um repositório público, é possível que um mantenedor com acesso de gravação tenha de aprovar qualquer execução de fluxo de trabalho.'
+title: Approving workflow runs from public forks
+intro: 'When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve any workflow runs.'
 versions:
   fpt: '*'
   ghec: '*'
 shortTitle: Approve public fork runs
-ms.openlocfilehash: b995362f67d97a3e2ee6d1029cbe24227867f58a
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145083634'
 ---
-## Sobre as execuções de fluxo de trabalho a partir de bifurcações públicas
+
+## About workflow runs from public forks
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-Você pode configurar os requisitos de aprovação de fluxo de trabalho para um [repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), uma [organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks) ou uma [empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
+You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
 
-As execuções de fluxo de trabalho que estão aguardando aprovação por mais de 30 dias são excluídas automaticamente.
+Workflow runs that have been awaiting approval for more than 30 days are automatically deleted.
 
-## Aprovando as execuções do fluxo de trabalho em um pull request a partir de uma bifurcação pública
+## Approving workflow runs on a pull request from a public fork
 
-Os mantenedores com acesso de gravação a um repositório podem usar o seguinte procedimento para revisar e executar fluxos de trabalho em pull requests de colaboradores que exigem aprovação.
-
-{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
-1. Inspecione as alterações propostas no pull request e certifique-se de que você esteja confortável em executar seus fluxos de trabalho no branch do pull request. Você deve ficar especialmente atento para todas as alterações propostas no diretório `.github/workflows/` que afetem arquivos de fluxo de trabalho.
-1. Se você estiver familiarizado com a execução de fluxos de trabalho no branch de solicitação de pull, volte à guia {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversa** e, em "Fluxos de trabalho que aguardam aprovação", clique em **Aprovar e executar**.
-
-   ![Aprovar e executar fluxos de trabalho](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
+{% data reusables.actions.workflows.approve-workflow-runs %}

translations/pt-BR/content/actions/managing-workflow-runs/index.md

@@ -1,6 +1,6 @@
 ---
 title: Gerenciar fluxos de trabalho
-shortTitle: Managing workflow runs
+shortTitle: Manage workflow runs
 intro: 'Você pode executar novamente ou cancelar um fluxo de trabalho, {% ifversion fpt or ghes or ghae %}examinar implantações, {% endif %}ver as minutas de execução de trabalhos faturáveis e baixar artefatos.'
 redirect_from:
   - /actions/configuring-and-managing-workflows/managing-a-workflow-run
@@ -18,17 +18,18 @@ children:
   - /re-running-workflows-and-jobs
   - /canceling-a-workflow
   - /approving-workflow-runs-from-public-forks
+  - /approving-workflow-runs-from-private-forks
   - /reviewing-deployments
   - /disabling-and-enabling-a-workflow
   - /skipping-workflow-runs
   - /deleting-a-workflow-run
   - /downloading-workflow-artifacts
   - /removing-workflow-artifacts
-ms.openlocfilehash: fe5f7c461fc03392bcc93713887b1cc1d4293207
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 9e7d6f9c29fdfb2a387b84373c1140dbb3ef6713
+ms.sourcegitcommit: 73b91dd4cdf592eadec4252319379d6fbe92858e
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145095094'
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164087'
 ---
 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}

translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md

@@ -49,19 +49,24 @@ For more information on workflow run artifacts, see "[Persisting workflow data u
 
 ## Restrictions for accessing a cache
 
-A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
+Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. 
+Workflow runs can restore caches created in either the current branch or the default branch (usually `main`). If a workflow run is triggered for a pull request, it can also restore caches created in the base branch, including base branches of forked repositories. For example, if the branch `feature-b` has the base branch `feature-a`, a workflow run triggered on a pull request would have access to caches created in the default `main` branch, the base `feature-a` branch, and the current `feature-b` branch.
 
-Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). On similar lines, a cache created for the tag `release-a` (from the base `main`) would not be accessible to a workflow triggered for the tag `release-b` (with the base `main`).
+Workflow runs cannot restore caches created for child branches or sibling branches. For example, a cache created for the child `feature-b` branch would not be accessible to a workflow run triggered on the parent `main` branch. Similarly, a cache created for the `feature-a` branch with the base `main` would not be accessible to its sibling `feature-c` branch with the base `main`. Workflow runs also cannot restore caches created for different tag names. For example, a cache created for the tag `release-a` with the base `main` would not be accessible to a workflow run triggered for the tag `release-b` with the base `main`.
 
-Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
+When a cache is created by a workflow run triggered on a pull request, the cache is created for the merge ref (`refs/pull/.../merge`). Because of this, the cache will have a limited scope and can only be restored by re-runs of the pull request. It cannot be restored by the base branch or other pull requests targeting that base branch.
+
+Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch.
 
 ## Using the `cache` action
 
-The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
+The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache that _exactly_ matches the key, the action restores the cached files to the `path` you configure.
+You can optionally provide a list of `restore-keys` to use in case the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can _partially_ match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
 
-If there is no exact match, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`.
+If there is an exact match to the provided `key`, this is considered a cache hit. If no cache exactly matches the provided `key`, this is considered a cache miss. On a cache miss, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. For more information about how this is handled, see "[Cache hits and misses](#cache-hits-and-misses)."
+
+You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key.
 
-You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
 
 ### Input parameters for the `cache` action
 
@@ -94,6 +99,21 @@ You can optionally provide a list of `restore-keys` to use when the `key` doesn'
 
 - `cache-hit`: A boolean value to indicate an exact match was found for the key.
 
+### Cache hits and misses
+When `key` exactly matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
+
+When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
+
+When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
+
+1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
+   - When there is an exact match, the action restores the files in the cache to the `path` directory.
+   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
+1. The `cache` action completes and the next step in the job runs.
+1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
+
+For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)."
+
 ### Example using the `cache` action
 
 This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
@@ -136,20 +156,6 @@ jobs:
         run: npm test
 ```
 
-When `key` matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
-
-When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
-
-When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
-
-1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
-   - When there is an exact match, the action restores the files in the cache to the `path` directory.
-   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
-1. The `cache` action completes and the next step in the job runs.
-1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
-
-For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)." Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
-
 ### Using contexts to create cache keys
 
 A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Expressions](/actions/learn-github-actions/expressions)."
@@ -185,7 +191,9 @@ In the example workflow above, there is a step that lists the state of the Node
 
 ## Matching a cache key
 
-The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
+The `cache` action first searches for cache hits for `key` and the cache _version_ in the branch containing the workflow run. If there is no hit, it searches for `restore-keys` and the _version_. If there are still no hits in the current branch, the `cache` action retries same steps on the default branch. Please note that the scope restrictions apply during the search. For more information, see "[Restrictions for accessing a cache](#restrictions-for-accessing-a-cache)."
+
+Cache version is a way to stamp a cache with metadata of the `path` and the compression tool used while creating the cache. This ensures that the consuming workflow run uniquely matches a cache it can actually decompress and use. For more information, see [Cache Version](https://github.com/actions/cache#cache-version) in the Actions Cache documentation.
 
 `restore-keys` allows you to specify a list of alternate restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches the `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
 

translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md

@@ -1,6 +1,6 @@
 ---
-title: About GitHub Connect
-intro: '{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by giving you access to additional features and workflows that rely on the power of {% data variables.product.prodname_dotcom_the_website %}.'
+title: Sobre o GitHub Connect
+intro: '{% data variables.product.prodname_github_connect %} melhora {% data variables.product.product_name %} dando-lhe acesso a funcionalidades e fluxos de trabalho adicionais que dependem do poder de {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   ghes: '*'
   ghae: '*'
@@ -9,76 +9,66 @@ topics:
   - Enterprise
   - GitHub Connect
 miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: ac4ec1d8b619e56c38013f5ae38d5782b6faec88
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160813'
 ---
+## Sobre o {% data variables.product.prodname_github_connect %}
 
-## About {% data variables.product.prodname_github_connect %}
+O {% data variables.product.prodname_github_connect %} aprimora o {% data variables.product.product_name %}, o que permite que o {% data variables.location.product_location %} se beneficie do poder do {% data variables.product.prodname_dotcom_the_website %} de maneira limitada. Depois de habilitar o {% data variables.product.prodname_github_connect %}, é possível habilitar recursos e fluxos de trabalho adicionais que dependem do {% data variables.product.prodname_dotcom_the_website %}, como o {% data variables.product.prodname_dependabot_alerts %}, para vulnerabilidades de segurança acompanhadas no {% data variables.product.prodname_advisory_database %}.
 
-{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.location.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. 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 {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}.
+O {% data variables.product.prodname_github_connect %} não abre o {% data variables.location.product_location %} para a Internet pública. 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 os dados que são transmitidos pelo {% data variables.product.prodname_github_connect %}, confira "[Transmissão de dados para o {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)".
 
-{% data variables.product.prodname_github_connect %} does not open {% data variables.location.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)."
+Habilitar {% data variables.product.prodname_github_connect %} não permitirá que usuários de {% data variables.product.prodname_dotcom_the_website %} façam alterações em {% data variables.product.product_name %}.
 
-Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}.
+Para habilitar o {% data variables.product.prodname_github_connect %}, você configura uma conexão entre o {% data variables.location.product_location %} e uma conta da organização ou uma conta corporativa no {% data variables.product.prodname_dotcom_the_website %} que usa o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} Para obter mais informações, confira "[Como gerenciar o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)".
 
-To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+Após habilitar a licença {% data variables.product.prodname_github_connect %}, você poderá habilitar funcionalidades como {% ifversion ghes %} a sincronização automática de licença de usuário e {% endif %}{% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações sobre todos os recursos disponíveis, confira "[Recursos do {% data variables.product.prodname_github_connect %}](#github-connect-features)".
 
-After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)."
+## Funcionalidades de {% data variables.product.prodname_github_connect %}
 
-## {% data variables.product.prodname_github_connect %} features
+Depois de configurar a conexão entre o {% data variables.location.product_location %} e o {% data variables.product.prodname_ghe_cloud %}, você pode habilitar recursos individuais do {% data variables.product.prodname_github_connect %} para sua empresa.
 
-After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise.
+Recurso | Descrição | Mais informações | ------- | ----------- | ---------------- | {% ifversion ghes %} Sincronização automática da licença de usuário | Gerencie o uso de licença nas suas implantações do {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuário do {% data variables.location.product_location %} com o {% data variables.product.prodname_ghe_cloud %}. | "[Habilitar 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 %} | Permitir que os usuários encontrem e corrijam vulnerabilidades em dependências de código. | "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} Ações do {% data variables.product.prodname_dotcom_the_website %} | Permita que os usuários usem ações do {% data variables.product.prodname_dotcom_the_website %} em arquivos de fluxo de trabalho. | "[Como habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | Analise seus dados agregados do GitHub Enterprise Server e nos ajude a aprimorar os produtos GitHub. | "[Como habilitar as {% data variables.product.prodname_server_statistics %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} Pesquisa unificada | Permita que os usuários incluam repositórios no {% data variables.product.prodname_dotcom_the_website %} nos resultados da pesquisa do {% data variables.location.product_location %}. | "[Como habilitar a {% data variables.enterprise.prodname_unified_search %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" Contribuições unificadas | Permita que os usuários incluam contagens de contribuição anônimas para os respectivos trabalhos do {% data variables.location.product_location %} nos grafos de contribuição do {% data variables.product.prodname_dotcom_the_website %}. | "[Como habilitar as {% data variables.enterprise.prodname_unified_contributions %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"
 
-Feature | Description | More information |
-------- | ----------- | ---------------- |{% ifversion ghes %}
-Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% 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 %}
-{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %}
-{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %}
-{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %}
-Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"
-Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.enterprise.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"
+## Transmissão de dados para {% data variables.product.prodname_github_connect %} 
 
-## Data transmission for {% data variables.product.prodname_github_connect %} 
-
-When {% data variables.product.prodname_github_connect %} is enabled, a record on {% data variables.product.prodname_ghe_cloud %} stores information about the connection. If you enable individual features of {% data variables.product.prodname_github_connect %}, additional data is transmitted.
+Quando {% data variables.product.prodname_github_connect %} está habilitada, um registro em {% data variables.product.prodname_ghe_cloud %} armazena informações sobre a conexão. Os dados adicionais são transmitidos se você habilitar os recursos individuais de {% data variables.product.prodname_github_connect %}.
 
 {% note %}
 
-**Note:** No repositories, issues, or pull requests are ever transmitted from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} by {% data variables.product.prodname_github_connect %}.
+**Observação:** nenhum repositório, problema ou solicitação de pull é transmitido do {% data variables.product.product_name %} para o {% data variables.product.prodname_dotcom_the_website %} pelo {% data variables.product.prodname_github_connect %}.
 
 {% endnote %}
 
-### Data transmitted when {% data variables.product.prodname_github_connect %} is enabled
+### Dados transmitidos quando {% data variables.product.prodname_github_connect %} estiver habilitado
 
-When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection.
+Ao habilitar {% data variables.product.prodname_github_connect %} ou funcionalidades específicas de{% data variables.product.prodname_github_connect %}, um registro em {% data variables.product.prodname_ghe_cloud %} irá armazenar as seguintes informações sobre a conexão.
 {% ifversion ghes %}
-- The public key portion of your {% data variables.product.prodname_ghe_server %} license
-- A hash of your {% data variables.product.prodname_ghe_server %} license
-- The customer name on your {% data variables.product.prodname_ghe_server %} license
-- The version of {% data variables.location.product_location_enterprise %}{% endif %}
-- The hostname of {% data variables.location.product_location %}
-- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.location.product_location %}
-- The authentication token that's used by {% data variables.location.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %}
-- If Transport Layer Security (TLS) is enabled and configured on {% data variables.location.product_location %}{% ifversion ghes %}
-- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.location.product_location %}, and the date and time of enablement{% endif %}
-- The dormancy threshold for your enterprise
-- The number of dormant users for your enterprise
-- A count of license-consuming seats, which does not include suspended users
+- A parte da chave pública da sua licença do {% data variables.product.prodname_ghe_server %};
+- Um hash da sua licença do {% data variables.product.prodname_ghe_server %};
+- O nome do cliente da sua licença do {% data variables.product.prodname_ghe_server %};
+- A versão do {% data variables.location.product_location_enterprise %}{% endif %}
+- O nome do host do {% data variables.location.product_location %}
+- A conta da organização ou a conta corporativa no {% data variables.product.prodname_ghe_cloud %} que está conectada ao {% data variables.location.product_location %}
+- O token de autenticação usado pelo {% data variables.location.product_location %} para fazer solicitações ao {% data variables.product.prodname_ghe_cloud %}
+- Se o protocolo TLS estiver habilitado e configurado no {% data variables.location.product_location %}{% ifversion ghes %}
+- Os recursos do {% data variables.product.prodname_github_connect %} que estão habilitados no {% data variables.location.product_location %} e a data e a hora da habilitação{% endif %}
+- O limite de inatividade para sua empresa
+- O número de usuários inativos para sua empresa
+- Uma contagem de estações que consomem a licença, que não inclui usuários suspensos
 
-{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled.
+O {% data variables.product.prodname_github_connect %} sincroniza os dados da conexão acima entre o {% data variables.location.product_location %} e o {% data variables.product.prodname_ghe_cloud %} semanalmente, a partir do dia e da hora aproximada que o {% data variables.product.prodname_github_connect %} foi habilitado.
 
-### Data transmitted by individual features of {% data variables.product.prodname_github_connect %}
+### Dados transmitidos por recursos individuais de {% data variables.product.prodname_github_connect %}
 
-Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}.
+Os dados adicionais são transmitidos se você habilitar as funcionalidades individuais de {% data variables.product.prodname_github_connect %}.
 
-Feature | Data | Which way does the data flow? | Where is the data used? | 
-------- | ---- | --------- | ------ |{% ifversion ghes %}
-Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %}
-{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %}
-{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository<br><br>If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %}
-{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %}
-{% data variables.product.prodname_server_statistics %} | Aggregate metrics about your usage of {% data variables.product.prodname_ghe_server %}. For the complete list of metrics, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %}
-Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} |
-Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} |
+Recurso | Dados | De que forma os dados fluem? | Onde os dados são usados? | ------- | ---- | --------- | ------ |{% ifversion ghes %} Sincronização automática de licença de usuário | ID de usuário e endereços de email de cada usuário do {% data variables.product.product_name %} | Do {% data variables.product.product_name %} para o {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidade | Do {% data variables.product.prodname_dotcom_the_website %} para o {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | As dependências e os metadados de cada repositório de dependência<br><br>Se uma dependência for armazenada em um repositório privado no {% data variables.product.prodname_dotcom_the_website %}, os dados só serão transmitidos se o {% data variables.product.prodname_dependabot %} estiver configurado e autorizado para acessar esse repositório. | Do {% data variables.product.prodname_dotcom_the_website %} para o {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} Ações do {% data variables.product.prodname_dotcom_the_website %} | Nome da ação, ação (arquivo YAML do {% data variables.product.prodname_marketplace %}) | Do {% data variables.product.prodname_dotcom_the_website %} para o {% data variables.product.product_name %}<br><br>De {% data variables.product.product_name %} até {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | Agregar métricas de uso do {% data variables.product.prodname_ghe_server %}. Para obter a lista completa de métricas, confira "[Sobre {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | De {% data variables.product.product_name %} a {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} {% endif %} | Pesquisa unificada | Termos de pesquisa, resultados da pesquisa | De {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.product_name %}<br><br>Do {% data variables.product.product_name %} para o {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | Contribuições unificadas | Contagens de contribuições | Do {% data variables.product.product_name %} para o {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} |
 
-## Further reading
+## Leitura adicional
 
-- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation
+- "[Contas Enterprise](/graphql/guides/managing-enterprise-accounts)" na documentação da API do GraphQL

translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md

@@ -1,7 +1,7 @@
 ---
-title: Managing GitHub Connect
+title: Gerenciando o GitHub Connect
 shortTitle: Manage GitHub Connect
-intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.location.product_location %}.'
+intro: 'Habilite o {% data variables.product.prodname_github_connect %} para acessar recursos e fluxos de trabalho adicionais do {% data variables.location.product_location %}.'
 redirect_from:
   - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com
   - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
@@ -20,71 +20,65 @@ topics:
   - GitHub Connect
   - Infrastructure
   - Networking
+ms.openlocfilehash: 30a170543b63c390aa8975b1ca57c265bc7fa8fa
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160645'
 ---
-
 {% data reusables.github-connect.beta %}
 
-## About {% data variables.product.prodname_github_connect %}
+## Sobre o {% data variables.product.prodname_github_connect %}
 
-You can access additional features and workflows on {% data variables.location.product_location %} by enabling {% data variables.product.prodname_github_connect %}. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
+Acesse recursos e fluxos de trabalho adicionais do {% data variables.location.product_location %}, habilitando o {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
 
-When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %}
+Ao habilitar o {% data variables.product.prodname_github_connect %}, você configura uma conexão entre o {% data variables.location.product_location %} e uma conta da organização ou uma conta corporativa no {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %}
 
-Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}.
+A habilitação de {% data variables.product.prodname_github_connect %} cria um {% data variables.product.prodname_github_app %} pertencente à organização ou conta corporativa em {% data variables.product.prodname_ghe_cloud %}. O {% data variables.product.product_name %} usa as credenciais do {% data variables.product.prodname_github_app %} para fazer solicitações ao {% data variables.product.prodname_ghe_cloud %}.
 
-{% ifversion ghes %}
-{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}.
-- An authentication token, which is valid for one hour
-- A private key, which is used to generate a new authentication token
+{% ifversion ghes %}O {% data variables.product.prodname_ghe_server %} armazena as credenciais dos {% data variables.product.prodname_github_app %}. As credenciais a seguir serão replicadas em todos os nós em um ambiente de alta disponibilidade ou de agrupamento e armazenadas em qualquer backup, incluindo instantâneos criados por {% data variables.product.prodname_enterprise_backup_utilities %}.
+- Um token de autenticação válido por uma hora;
+- Uma chave privada, que é usada para gerar um novo token de autenticação {% endif %}
+
+## Pré-requisitos
+
+Para usar {% data variables.product.prodname_github_connect %}, você deve ter uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} que use {% data variables.product.prodname_ghe_cloud %}. Você pode já ter {% data variables.product.prodname_ghe_cloud %} incluído no seu plano. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% ifversion ghes %} Se a sua conta da organização ou conta corporativa do {% data variables.product.prodname_dotcom_the_website %} usar listas de IP permitidos, você precisará adicionar o endereço IP ou a rede do {% data variables.location.product_location %} à lista de IPs permitidos no {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como gerenciar endereços IP permitidos para sua organização](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" e "[Como impor políticas para configurações de segurança na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" na documentação do {% data variables.product.prodname_ghe_cloud %}.
+
+Para configurar uma conexão, sua configuração de proxy precisa permitir a conectividade com `github.com`, `api.github.com` e `uploads.github.com`. Para obter mais informações, confira "[Como configurar um servidor proxy Web de saída](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)".
 {% endif %}
 
-## Prerequisites
+## Habilitar o {% data variables.product.prodname_github_connect %}
 
-To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %}
+Os proprietários corporativos que também são proprietários da conta de uma organização ou empresa que usa {% data variables.product.prodname_ghe_cloud %} podem habilitar {% data variables.product.prodname_github_connect %}.
+
+Se você estiver conectando o {% data variables.location.product_location %} a uma organização no {% data variables.product.prodname_ghe_cloud %} que não seja propriedade de uma conta corporativa, precisará entrar no {% data variables.product.prodname_dotcom_the_website %} como proprietário da organização.
+
+Se você estiver conectando o {% data variables.location.product_location %} a uma organização no {% data variables.product.prodname_ghe_cloud %} que pertença a uma conta corporativa ou a uma conta corporativa própria, precisará entrar no {% data variables.product.prodname_dotcom_the_website %} como proprietário da empresa.
 
 {% ifversion ghes %}
-If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.location.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
-
-To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)."
-{% endif %}
-
-## Enabling {% data variables.product.prodname_github_connect %}
-
-Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}.
-
-If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner.
-
-If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner.
-
-{% ifversion ghes %}
-1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
-1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+1. Entre no {% data variables.location.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. Entre no {% data variables.location.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}.
 {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
-1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features</a>."
-{% ifversion ghes %}
-  ![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %}
-  ![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png)
-{% endif %}
-1. Next to the enterprise account or organization you'd like to connect, click **Connect**.
-  ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
+1. Em "O {% data variables.product.prodname_github_connect %} ainda não está habilitado", clique em **Habilitar o {% data variables.product.prodname_github_connect %}** . Ao clicar em **Habilitar o {% data variables.product.prodname_github_connect %}** , você concorda com os "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">Termos de Produtos e Recursos Adicionais do {% data variables.product.prodname_dotcom %}</a>".
+{% ifversion ghes %} ![Botão Habilitar o GitHub Connect](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} ![Botão Habilitar o GitHub Connect](/assets/images/enterprise/github-ae/enable-github-connect-button.png) {% endif %}
+1. Ao lado da conta corporativa ou de organização que deseja conectar, clique em **Conectar**.
+  ![Botão Conectar ao lado de uma conta corporativa ou de empresa](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
 
-## Disabling {% data variables.product.prodname_github_connect %}
+## Como desabilitar o {% data variables.product.prodname_github_connect %}
 
-Enterprise owners can disable {% data variables.product.prodname_github_connect %}.
+Os proprietários das empresas podem desabilitar {% data variables.product.prodname_github_connect %}.
 
-When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.location.product_location %} are deleted.
+Quando você se desconecta do {% data variables.product.prodname_ghe_cloud %}, o {% data variables.product.prodname_github_app %} do {% data variables.product.prodname_github_connect %} é excluído da sua conta corporativa ou da sua conta da organização e as credenciais armazenadas no {% data variables.location.product_location %} são excluídas.
 
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**.
-{% ifversion ghes %}
-  ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
-1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
-  ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)  
-{% else %}
-  ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/github-ae/disable-github-connect-button.png)
-1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
-  ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png)
-{% endif %} 
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+1. Ao lado da conta corporativa ou de organização que deseja desconectar, clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** .
+{% ifversion ghes %} ![Botão Desabilitar o GitHub Connect ao lado de uma conta corporativa ou de um nome de organização](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
+1. Leia as informações sobre como desconectar e clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** .
+  ![Caixa de diálogo modal com informações de aviso sobre a desconexão e botão de confirmação](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)  
+{% else %} ![Botão Desabilitar o GitHub Connect ao lado de uma conta corporativa ou de um nome de organização](/assets/images/enterprise/github-ae/disable-github-connect-button.png)
+1. Leia as informações sobre como desconectar e clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** .
+  ![Caixa de diálogo modal com informações de aviso sobre a desconexão e botão de confirmação](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) {% endif %} 

translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md

@@ -1,5 +1,5 @@
 ---
-title: Network ports
+title: Portas de rede
 redirect_from:
   - /enterprise/admin/articles/configuring-firewalls
   - /enterprise/admin/articles/firewall
@@ -8,7 +8,7 @@ redirect_from:
   - /enterprise/admin/installation/network-ports
   - /enterprise/admin/configuration/network-ports
   - /admin/configuration/network-ports
-intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
+intro: 'Abra as portas de rede seletivamente com base nos serviços que você precisa expor para administradores, usuários finais e suporte por e-mail.'
 versions:
   ghes: '*'
 type: reference
@@ -17,56 +17,62 @@ topics:
   - Infrastructure
   - Networking
   - Security
+ms.openlocfilehash: 048b27ed44cea11057c781ae3043078a825f8d1a
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160647'
 ---
-## Administrative ports
+## Portas administrativas
 
-Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
+Algumas portas administrativas precisam configurar o {% data variables.location.product_location %} e executar determinados recursos. Não é preciso haver portas administrativas para os usuários finais aproveitarem os recursos básicos do aplicativo.
 
-| Port | Service | Description |
+| Porta | Serviço | Descrição |
 |---|---|---|
-| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
-| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. |
-| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
-| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
-| 123/UDP| NTP | Required for time protocol operation. |
-| 161/UDP | SNMP | Required for network monitoring protocol operation. |
+| 8443 | HTTPS | {% data variables.enterprise.management_console %} seguro na web. Obrigatória para instalação e configuração básicas. |
+| 8080 | HTTP | {% data variables.enterprise.management_console %} de texto simples na web. Não é obrigatória, a menos que o TSL seja desabilitado manualmente. |
+| 122 | SSH | Acesso de shell ao {% data variables.location.product_location %}. Obrigatório para estar aberto a conexões de entrada entre todos os nós em uma configuração de alta disponibilidade. A porta SSH padrão (22) é dedicada ao tráfego de rede de aplicativos Git e SSH. |
+| 1194/UDP | VPN | Túnel de rede de réplica segura na configuração de alta disponibilidade. Obrigatório estar aberto para a comunicação entre todos os nós da configuração.|
+| 123/UDP| NTP | Obrigatória para operações de protocolo de tempo. |
+| 161/UDP | SNMP | Obrigatória para operações de protocolo de monitoramento de rede. |
 
-## Application ports for end users
+## Portas de aplicativo para usuários finais
 
-Application ports provide web application and Git access for end users.
+As portas de aplicativo fornecem aplicativos da web e acesso dos usuários finais ao Git.
 
-| Port | Service | Description |
+| Porta | Serviço | Descrição |
 |---|---|---|
-| 443 | HTTPS | Access to the web application and Git over HTTPS. |
-| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. |
-| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
-| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
+| 443 | HTTPS | Acesso ao aplicativo da web e ao Git por HTTPS. |
+| 80 | HTTP | Acesso ao aplicativo da web. Todas as solicitações são redirecionadas para a porta HTTPS se o TLS estiver configurado. |
+| 22 | SSH | Acesso ao Git por SSH. Compatível com operações de clonagem, fetch e push em repositórios públicos e privados. |
+| 9418 | Git | A porta do protocolo Git é compatível com operações de clonagem e fetch em repositórios públicos com comunicação de rede não criptografada. {% data reusables.enterprise_installation.when-9418-necessary %} |
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Email ports
+## Portas de e-mail
 
-Email ports must be accessible directly or via relay for inbound email support for end users.
+As portas de e-mail devem estar acessíveis diretamente ou via retransmissão para oferecer suporte de e-mail aos usuários finais.
 
-| Port | Service | Description |
+| Porta | Serviço | Descrição |
 |---|---|---|
-| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
+| 25 | SMTP | Suporte a SMTP com criptografia (STARTTLS). |
 
-## {% data variables.product.prodname_actions %} ports
+## Portas de {% data variables.product.prodname_actions %}
 
-{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)."
+As portas do {% data variables.product.prodname_actions %} precisam estar acessíveis para os executores auto-hospedados se conectarem ao {% data variables.location.product_location %}. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)".
 
-| Port | Service | Description |
+| Porta | Serviço | Descrição |
 |---|---|---|
-| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured.
-| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured.
+| 443 | HTTPS | Os executores auto-hospedados se conectam ao {% data variables.location.product_location %} para receber atribuições de trabalho e baixar as novas versões do aplicativo do executor. Obrigatório se TLS estiver configurado.
+| 80 | HTTP | Os executores auto-hospedados se conectam ao {% data variables.location.product_location %} para receber atribuições de trabalho e baixar as novas versões do aplicativo do executor. Obrigatório se TLS não estiver configurado.
 
-If you enable automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, {% data variables.product.prodname_actions %} will always search for an action on {% data variables.location.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)."
+Se você habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %}, o {% data variables.product.prodname_actions %} sempre pesquisará uma ação no {% data variables.location.product_location %} primeiro, por meio dessas portas, antes de verificar o {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)".
 
-## {% data variables.product.prodname_github_connect %} ports
+## Portas do {% data variables.product.prodname_github_connect %}
 
-If you enable {% data variables.product.prodname_github_connect %}, the connection between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %} uses HTTPS over ports 443 or 80, and TLS is required. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
+Se você habilitar o {% data variables.product.prodname_github_connect %}, a conexão entre o {% data variables.product.product_name %} e o {% data variables.product.prodname_dotcom_the_website %} usará HTTPS nas portas 443 ou 80 e o TLS será necessário. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
 
-## Further reading
+## Leitura adicional
 
-- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)"
+- "[Como configurar o TLS](/admin/configuration/configuring-network-settings/configuring-tls)"

translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md

@@ -1,7 +1,7 @@
 ---
-title: About {% data variables.product.prodname_emus %}
+title: 'Sobre os {% data variables.product.prodname_emus %}'
 shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+intro: 'Você pode gerenciar centralmente a identidade e o acesso dos integrantes da empresa em {% data variables.product.prodname_dotcom %} a partir do seu provedor de identidade.'
 redirect_from:
   - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
@@ -17,48 +17,53 @@ topics:
   - Enterprise
   - SSO
 allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 82a8b8c29ea38d57f0481146f2a857c2dcba8413
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160725'
 ---
+## Sobre os {% data variables.product.prodname_emus %}
 
-## About {% data variables.product.prodname_emus %}
+Com {% data variables.product.prodname_emus %}, você pode controlar as contas de usuário dos integrantes da empresa por meio do provedor de identidade (IdP). Os usuários atribuídos ao aplicativo {% data variables.product.prodname_emu_idp_application %} no seu IdP são provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} e adicionados à sua empresa. Você controla nomes de usuários, dados de perfil, associações a equipes e acesso a repositórios das contas de usuário por meio do IdP.
 
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
-
-In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+No IdP, você pode dar a cada {% data variables.enterprise.prodname_managed_user %} a função do proprietário corporativo, usuário ou gerente de cobrança. {% data variables.enterprise.prodname_managed_users_caps %} podem ter organizações dentro da empresa e adicionar outros {% data variables.enterprise.prodname_managed_users %} às organizações e equipes internamente. Para obter mais informações, confira "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" e "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
 
 {% ifversion oidc-for-emu %}
 
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %} Para obter mais informações, confira "[Sobre o suporte à política de acesso condicional do IdP](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)".
 
 {% endif %}
 
-You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
+Você pode permitir que os {% data variables.enterprise.prodname_managed_users %} acessem repositórios na empresa e contribuam neles, mas os {% data variables.enterprise.prodname_managed_users %} não podem criar conteúdo público nem colaborar com outros usuários, organizações e empresas no restante do {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Habilidades e restrições de {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)".
 
-The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Os nomes de usuários que são {% data variables.enterprise.prodname_managed_users %} da empresa e as respectivas informações de perfil como, nomes de exibição e endereços de email, são definidos por meio do IdP e não podem ser alterados pelos próprios usuários. Para obter mais informações, confira "[Nomes de usuário e informações de perfil](#usernames-and-profile-information)".
 
-Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
+Os proprietários corporativos podem auditar todas as ações de {% data variables.enterprise.prodname_managed_users %} no {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Eventos de log de auditoria da empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)".
 
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para obter mais informações sobre como criar essa conta, confira "[Sobre empresas com usuários gerenciados](#about-enterprises-with-managed-users)".
 
 {% note %}
 
-**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
+**Observação:** há várias opções para gerenciamento de identidade e acesso com o {% data variables.product.prodname_ghe_cloud %}. O {% data variables.product.prodname_emus %} não é a melhor solução para todos os clientes. Para saber se o {% data variables.product.prodname_emus %} é adequado para sua empresa, confira "[Sobre autenticação na sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)".
 
 {% endnote %}
 
-## About organization membership management
+## Sobre o gerenciamento de associação da organização
 
-Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+As associações da organização podem ser gerenciadas manualmente ou você pode atualizá-las automaticamente usando grupos do IdP. Para gerenciar associações da organização por meio do IdP, os membros precisam ser adicionados a um grupo do IdP e esse grupo precisa estar conectado a uma equipe dentro da organização. Para obter mais informações de como gerenciar a organização e a associação de equipe automaticamente, confira "[Como gerenciar associações de equipe com grupos de provedores de identidade](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)".
 
-The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization. 
+A maneira em que um membro é adicionado a uma organização pertencente à empresa (por meio de grupos do IdP ou manualmente) determina como ele deve ser removido de uma organização. 
 
-- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
-- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+- Se um membro foi adicionado a uma organização manualmente, você deverá removê-lo manualmente. O cancelamento a atribuição do aplicativo {% data variables.product.prodname_emu_idp_application %} no IdP suspende o usuário, mas não o remove da organização.
+- Se um usuário se tornou membro de uma organização porque foi adicionado a grupos do IdP mapeados para uma ou mais equipes na organização, quando ele for removido de _todos_ os grupos do IdP mapeados associados à organização, ele será removido da organização.
 
-To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+Para descobrir como um membro foi adicionado a uma organização, você pode filtrar a lista de membros por tipo. Para obter mais informações, confira "[Como ver os funcionários da sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)".
 
-## Identity provider support
+## Suporte do provedor de identidade
 
-{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
+O {% data variables.product.prodname_emus %} dá suporte aos seguintes métodos de autenticação e IdPs{% ifversion oidc-for-emu %}:
 
 |                                  | SAML                                          | OIDC (beta)                                   |
 |----------------------------------|-----------------------------------------------|-----------------------------------------------|
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
 
 {% endif %}
 
-## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
+## Habilidades e restrições de {% data variables.enterprise.prodname_managed_users %}
 
-{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
+Os {% data variables.enterprise.prodname_managed_users_caps %} só podem contribuir para repositórios privados e internos da empresa e repositórios privados pertencentes à conta de usuário. Os {% data variables.enterprise.prodname_managed_users_caps %} têm acesso somente leitura a toda a comunidade ampla do {% data variables.product.prodname_dotcom %}. Estas restrições de acesso e visibilidade para usuários e conteúdo aplicam-se a todas as solicitações, incluindo solicitações da API.
 
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises. 
-* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. 
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
-* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
-* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} não podem ser convidados para organizações ou repositórios fora da empresa e os {% data variables.enterprise.prodname_managed_users %} não podem ser convidados para outras empresas. 
+* Os colaboradores externos não são compatíveis com {% data variables.product.prodname_emus %}.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} não podem criar problemas em solicitações de pull, comentar ou adicionar reações, nem adicionar aos favoritos, fazer inspeção ou criar fork de repositórios fora da empresa.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} podem visualizar todos os repositórios públicos no {% data variables.product.prodname_dotcom_the_website %}, mas não podem enviar código por push a repositórios fora da empresa.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} e o conteúdo que criam é visível apenas para outros membros da empresa. 
+* Os {% data variables.enterprise.prodname_managed_users_caps %} não podem seguir usuários fora da empresa.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} não podem criar gists nem comentários em gists.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} não podem criar fluxos de trabalho iniciais para o {% data variables.product.prodname_actions %}.
+* Os {% data variables.enterprise.prodname_managed_users_caps %} não podem instalar {% data variables.product.prodname_github_apps %} nas contas de usuário.
+* Os outros usuários do {% data variables.product.prodname_dotcom %} não podem ver, mencionar nem convidar um {% data variables.enterprise.prodname_managed_user %} para colaborar.
+* Você pode escolher se os {% data variables.enterprise.prodname_managed_users %} podem criar repositórios pertencentes às respectivas contas de usuário. Para obter mais informações, confira "[Como impor políticas de gerenciamento de repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)".
+* Se você permitir que os {% data variables.enterprise.prodname_managed_users %} criem repositórios pertencentes às respectivas contas de usuário, eles só poderão ter repositórios privados e convidar outros membros corporativos para colaborar nos repositórios de propriedade do usuário.
 * {% data reusables.enterprise-accounts.emu-forks %}
-* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. 
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+* Apenas repositórios privados e internos podem ser criados em organizações pertencentes a um {% data variables.enterprise.prodname_emu_enterprise %}, dependendo das configurações de visibilidade da organização e do repositório corporativo. 
+* Os {% data variables.enterprise.prodname_managed_users_caps %} são limitados quanto ao uso de {% data variables.product.prodname_pages %}. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)".
 * {% data reusables.copilot.emus-cannot-use-copilot %}
 
-## Getting started with {% data variables.product.prodname_emus %}
+## Introdução aos {% data variables.product.prodname_emus %}
 
-Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
+Para que os desenvolvedores possam usar o {% data variables.product.prodname_ghe_cloud %} com o {% data variables.product.prodname_emus %}, você precisa seguir uma série de etapas de configuração.
 
-1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+1. Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para experimentar {% data variables.product.prodname_emus %} ou para discutir opções para a migração da sua empresa existente, entre em contato com a [Equipe de vendas do {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
   
-  Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+  Seu ponto de contato na equipe do GitHub Sales de vendas vai trabalhar com você para criar um {% data variables.enterprise.prodname_emu_enterprise %}. Você deverá fornecer o endereço de e-mail para o usuário que irá configurar sua empresa e um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} Para obter mais informações, confira "[Nomes de usuário e informações de perfil](#usernames-and-profile-information)".
   
-2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`. 
+2. Após criarmos sua empresa, você receberá um e-mail de {% data variables.product.prodname_dotcom %} convidando você a escolher uma senha para o usuário de configuração da sua empresa, que será o primeiro proprietário da empresa. Use uma janela de navegação anônima ou privada ao definir a senha. O usuário de configuração é usado apenas para configurar a integração entre o logon único e o provisionamento do SCIM para a empresa. Ele não terá mais acesso para administrar a conta empresarial quando o SSO for habilitado com sucesso. O nome do usuário de configuração é o código curto da sua empresa com o sufixo `_admin`. 
   
   {% note %}
   
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
   
   {% endnote %}
   
-3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+3. Depois que você entrar como o usuário de configuração, recomendamos que habilite a autenticação de dois fatores. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)".
 
-1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). Both options provide a seamless sign-in experience for your members, but only OIDC includes support for Conditional Access Policies (CAP). If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
+1. Para começar, configure {% ifversion oidc-for-emu %}como os membros serão autenticados. Se você estiver usando o Azure Active Directory como provedor de identidade, poderá escolher entre o OIDC (OpenID Connect) e o SAML (Security Assertion Markup Language). As duas opções oferecem uma experiência de entrada perfeita aos membros, mas apenas o OIDC inclui suporte para CAP (políticas de acesso condicional). Se você estiver usando o Okta como provedor de identidade, poderá usar o SAML para autenticar os membros.{% else %} SSO do SAML para sua empresa. Para obter mais informações, confira "[Como configurar o logon único do SAML para usuários empresariais gerenciados](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
   
   {% ifversion oidc-for-emu %}
   
-  To get started, read the guide for your chosen authentication method.
+  Para começar, leia o guia do método de autenticação escolhido.
   
-    - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
-    - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+    - "[Como configurar o OIDC para usuários empresariais gerenciados](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)".
+    - "[Como configurar o logon único do SAML para usuários empresariais gerenciados](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".
   
   {% endif %}
   
-4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+4. Depois de configurar o SSO, você poderá configurar o provisionamento do SCIM. O SCIM é a forma como o seu provedor de identidade criará {% data variables.enterprise.prodname_managed_users %} no {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações de como configurar o provisionamento do SCIM, confira "[Como configurar o provisionamento do SCIM para usuários empresariais gerenciados](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)".
   
-5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
+5. Depois que a autenticação e o provisionamento forem configurados, você poderá começar a gerenciar a associação à organização para os {% data variables.enterprise.prodname_managed_users %} sincronizando os grupos de IdP com as equipes. Para obter mais informações, confira "[Como gerenciar associações à equipe com grupos de provedores de identidade](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)".
 
-If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+Se os membros da sua empresa precisarem usar uma estação de trabalho para contribuir com os repositórios no {% data variables.location.product_location %} por meio de um {% data variables.enterprise.prodname_managed_user %} e de uma conta pessoal, você poderá fornecer suporte. Para obter mais informações, confira "[Suporte a desenvolvedores com várias contas de usuário em {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)".
 
-## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
+## Fazer a autenticação como um {% data variables.enterprise.prodname_managed_user %}
 
-{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. 
+Os {% data variables.enterprise.prodname_managed_users_caps %} precisam fazer a autenticação por meio do provedor de identidade. Para fazer a autenticação, um {% data variables.enterprise.prodname_managed_user %} pode acessar o portal do aplicativo do IdP ou usar a página de logon no {% data variables.product.prodname_dotcom_the_website %}. 
 
-By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
+Por padrão, quando um usuário não autenticado tenta acessar uma empresa que usa {% data variables.product.prodname_emus %}, o {% data variables.product.company_short %} exibe um erro 404. Opcionalmente, um proprietário corporativo pode habilitar redirecionamentos automáticos para SSO (logon único) em vez do 404. Para obter mais informações, confira "[Como impor políticas para configurações de segurança na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)".
 
-{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
+{% data reusables.enterprise-accounts.about-recovery-codes %} Para obter mais informações, confira "[Como gerenciar códigos de recuperação para sua empresa](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)".
 
-### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
+### Fazer a autenticação como {% data variables.enterprise.prodname_managed_user %} por meio do {% data variables.product.prodname_dotcom_the_website %}
 
-1. Navigate to [https://github.com/login](https://github.com/login).
-1. In the "Username or email address" text box, enter your username including the underscore and short code.
-  ![Screenshot showing login form](/assets/images/help/enterprises/emu-login-username.png)
-  When the form recognizes your username, the form will update. You do not need to enter your password on this form.
-1. To continue to your identity provider, click **Sign in with your identity provider**.
-  ![Screenshot showing "Sign in with your identity provider" button](/assets/images/help/enterprises/emu-login-submit.png)
+1. Navegue até [https://github.com/login](https://github.com/login).
+1. Na caixa de texto "Nome de usuário ou endereço de e-mail", insira seu nome de usuário, incluindo o sublinhado e o código curto.
+  ![Captura de tela mostrando o formulário de logon](/assets/images/help/enterprises/emu-login-username.png) Ao reconhecer seu nome de usuário, o formulário será atualizado. Você não precisa digitar sua senha neste formulário.
+1. Para continuar acessando o provedor de identidade, clique em **Entrar com seu provedor de identidade**.
+  ![Captura de tela mostrando o botão "Entrar com seu provedor de identidade"](/assets/images/help/enterprises/emu-login-submit.png)
 
-## Usernames and profile information
+## Nome de usuário e informações de perfil
 
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+O {% data variables.product.product_name %} cria automaticamente um nome de usuário para cada pessoa normalizando um identificador fornecido pelo IdP. Para obter mais informações, confira "[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)".
 
-A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
+Um conflito poderá ocorrer ao provisionar usuários se as partes exclusivas do identificador fornecidas pelo IdP forem removidas durante a normalização. Se você não puder provisionar um usuário devido a um conflito de nome de usuário, você deverá modificar o nome de usuário fornecido pelo IdP. Para obter mais informações, confira "[Como resolver problemas de nome de usuário](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)".
 
 {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} 
 
-The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
+O nome do perfil e o endereço de email de um {% data variables.enterprise.prodname_managed_user %} também é fornecido pelo IdP. Os {% data variables.enterprise.prodname_managed_users_caps %} não podem alterar o nome de perfil nem o endereço de email no {% data variables.product.prodname_dotcom %} e o IdP pode fornecer um só endereço de email.
 
-## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
+## Suporte a desenvolvedores com várias contas de usuário em {% data variables.location.product_location %}
 
-People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
+As pessoas da equipe talvez precisem contribuir com recursos em {% data variables.location.product_location %} que estão fora da {% data variables.enterprise.prodname_emu_enterprise %}. Por exemplo, talvez você deseje manter uma empresa separada para os projetos de código aberto da sua empresa. Como um {% data variables.enterprise.prodname_managed_user %} não pode contribuir com recursos públicos, os usuários precisarão manter uma conta pessoal separada para esse trabalho.
 
-People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+As pessoas que precisam contribuir com duas contas de usuário em {% data variables.location.product_location %} usando uma estação de trabalho podem configurar o Git para simplificar o processo. Para obter mais informações, confira "[Como gerenciar várias contas](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)".

translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md

@@ -1,7 +1,7 @@
 ---
-title: Configuring SCIM provisioning for Enterprise Managed Users with Okta
+title: Configurando o provisionamento do SCIM para usuários gerenciados pela empresa com Okta
 shortTitle: Set up provisioning with Okta
-intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider.
+intro: Você pode fornecer novos usuários e gerenciar os integrantes da sua empresa e das equipes usando o Okta como seu provedor de identidade.
 product: '{% data reusables.gated-features.emus %}'
 versions:
   ghec: '*'
@@ -17,81 +17,86 @@ topics:
   - Authentication
   - Enterprise
   - SSO
+ms.openlocfilehash: b8c086d1d91c1248fa5a0349bb6f8ef32c3bbdf0
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160709'
 ---
+## Sobre o provisionamento com Okta
 
-## About provisioning with Okta
+Você pode usar {% data variables.product.prodname_emus %} com o Okta como seu provedor de identidade para fornecer novas contas, gerenciar a associação da empresa e gerenciar as associações das equipes para as organizações na sua empresa. Para obter mais informações sobre o provisionamento dos {% data variables.product.prodname_emus %}, confira "[Como configurar o provisionamento do SCIM para usuários gerenciados corporativos](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)".
 
-You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+Antes de configurar o provisionamento com o Okta, você deverá configurar o logon único SAML. Para obter mais informações, confira "[Como configurar o logon único do SAML para os Usuários Gerenciados Corporativos](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".
 
-Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+Para configurar o provisionamento com o Okta, defina o nome da sua empresa no aplicativo {% data variables.product.prodname_emu_idp_application %} e insira o {% data variables.product.pat_generic %} do usuário da instalação. Em seguida, você poderá começar a provisionar usuários no Okta.
 
-To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta.
+## Recursos compatíveis
 
-## Supported features
+{% data variables.product.prodname_emus %} é compatível com muitas funcionalidades no Okta.
 
-{% data variables.product.prodname_emus %} supports many provisioning features in Okta.
-
-| Feature | Description |
+| Recurso | Descrição |
 | --- | --- |
-| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. |
-| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. |
-| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. |
-| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. |
-| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. |
+| Fazer push de novos usuários | Os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no Okta são automaticamente criados na empresa em {% data variables.product.product_name %}. |
+| Fazer push da atualização do perfil | As atualizações feitas no perfil do usuário no Okta serão enviadas por push para {% data variables.product.product_name %}. |
+| Grupos de Push | Os grupos no Okta atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} como os Grupos Push são criados automaticamente na empresa em {% data variables.product.product_name %}. |
+| Fazer push de desativações de usuário | Cancelar a atribuição do usuário do aplicativo de {% data variables.product.prodname_emu_idp_application %} no Okta irá desabilitar o usuário em {% data variables.product.product_name %}. O usuário não poderá efetuar o login, mas as informações do usuário serão mantidas. |
+| Reativar usuários | Os Usuários do Okta cujas contas do Okta são reativadas e atribuídas de volta ao aplicativo de {% data variables.product.prodname_emu_idp_application %} serão habilitados. |
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames.
+**Observação:** os {% data variables.product.prodname_emus %} não dão suporte a modificações em nomes de usuário.
 
 {% endnote %}
 
-## Setting your enterprise name
+## Configurando o nome da sua empresa
 
-After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta.
+Após a criação do {% data variables.enterprise.prodname_emu_enterprise %}, você poderá começar a configurar o provisionamento definindo o nome da sua empresa no Okta.
 
-1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
-1. Click the **Sign On** tab.
-1. To make changes, click **Edit**.
-1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc".
-![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png)
-1. To save your enterprise name, click **Save**.
+1. Acesse o seu aplicativo de{% data variables.product.prodname_emu_idp_application %} no Okta.
+1. Clique na guia **Logon**.
+1. Para fazer alterações, clique em **Editar**.
+1. Em "Configurações Avançadas de Login", na caixa de texto "Nome da empresa", digite o nome da sua empresa. Por exemplo, se você acessar sua empresa em `https://github.com/enterprises/octoinc`, o nome da empresa será "octoinc".
+![Captura de tela do campo Nome da Empresa no Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png)
+1. Para salvar o nome da empresa, clique em **Salvar**.
 
-## Configuring provisioning
+## Configurando o provisionamento
 
-After setting your enterprise name, you can proceed to configure provisioning settings.
+Após definir o nome da sua empresa, você poderá prosseguir para definir as configurações de provisionamento.
 
-To configure provisioning, the setup user with the **@<em>SHORT-CODE</em>_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)."
+Para configurar o provisionamento, o usuário da instalação com o nome de usuário **@<em>SHORT-CODE</em>_admin** precisará fornecer um {% data variables.product.pat_v1 %} com o escopo **admin:enterprise**. Para obter mais informações sobre como criar um token, confira "[Como criar um {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)".
 
-1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
-1. Click the **Provisioning** tab.
-1. In the settings menu, click **Integration**.
-1. To make changes, click **Edit**.
-1. Select **Enable API integration**.
-1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user.
-![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png)
-1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen.
-1. To save the token, click **Save**.
-1. In the settings menu, click **To App**.
-![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png)
-1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**.
-1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**.
-![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png)
-1. To finish configuring provisioning, click **Save**.
+1. Acesse o seu aplicativo de{% data variables.product.prodname_emu_idp_application %} no Okta.
+1. Clique o **provisionamento** guia.
+1. No menu de configurações, clique em **Integração**.
+1. Para fazer alterações, clique em **Editar**.
+1. Selecione **Habilitar integração de API**.
+1. No campo "Token de API", insira o {% data variables.product.pat_v1 %} com o escopo **admin:enterprise** pertencente ao usuário da instalação.
+![Captura de tela que mostra o campo Token de API no Okta](/assets/images/help/enterprises/okta-emu-token.png)
+1. Clique em **Testar Credenciais da API**. Se o teste for bem sucedido, será exibida uma mensagem de verificação na parte superior da tela.
+1. Para salvar o token, clique em **Salvar**.
+1. No menu de configurações, clique em **No Aplicativo**.
+![Captura de tela que mostra o item de menu No Aplicativo no Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png)
+1. À direita de "Provisionamento no Aplicativo", para permitir que as alterações sejam feitas, clique em **Editar**.
+1. Selecione **Habilitar** para **Criar Usuários**, **Atualizar Atributos de Usuário** e **Desativar Usuários**.
+![Captura de tela que mostra as opções de provisionamento no Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png)
+1. Para concluir a configuração do provisionamento, clique em **Salvar**.
 
-## Assigning users and groups
+## Atribuindo usuários e grupos
 
-After you have configured SAML SSO and provisioning, you will be able to provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users or groups to the {% data variables.product.prodname_emu_idp_application %} application. 
+Depois de configurar o SSO do SAML e o provisionamento, você poderá provisionar novos usuários no {% data variables.product.prodname_dotcom_the_website %} atribuindo usuários ou grupos ao aplicativo {% data variables.product.prodname_emu_idp_application %}. 
 
 {% data reusables.scim.emu-scim-rate-limit %}
 
-You can also automatically manage organization membership by adding groups to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+Você também pode gerenciar automaticamente a associação à organização atribuindo grupos à guia "Grupos de Push" no Okta. Quando o grupo for provisionado com sucesso, ele estará disponível para conectar-se a equipes das organizações da empresa. Para obter mais informações sobre como gerenciar equipes, confira "[Como gerenciar associações à equipe com grupos de provedores de identidade](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)".
 
-When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+Ao atribuir aos usuários, você poderá usar o atributo "Funções" no aplicativo de {% data variables.product.prodname_emu_idp_application %} para definir a função de um usuário na sua empresa em {% data variables.product.product_name %}. Para obter mais informações sobre funções, confira "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)".
 
-![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png)
+![Captura de tela que mostra as opções da função para o usuário provisionado do Okta](/assets/images/help/enterprises/okta-emu-user-role.png)
 
-## Deprovisioning users and groups
+## Desprovisionar usuários e grupos
 
-To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab.
+Para remover um usuário ou grupo de {% data variables.product.product_name %}, remova o usuário ou o grupo da guia "Atribuições" e da guia "Grupos de push" no Okta. Para usuários, verifique se o usuário foi removido de todos os grupos na guia "Grupos de Push".
 
 

translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md

@@ -1,7 +1,7 @@
 ---
-title: Managing team memberships with identity provider groups
+title: Gerenciando associações de equipes com grupos de provedores de identidade
 shortTitle: Manage teams with your IdP
-intro: 'You can manage team and organization membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with teams within your {% data variables.enterprise.prodname_emu_enterprise %}.'
+intro: 'Você pode gerenciar a associação à equipe e à organização no {% data variables.product.product_name %} por meio do IdP (provedor de identidade) conectando os grupos de IdP às equipes no {% data variables.enterprise.prodname_emu_enterprise %}.'
 product: '{% data reusables.gated-features.emus %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups
@@ -16,77 +16,74 @@ topics:
   - Enterprise
   - SSO
   - Teams
+ms.openlocfilehash: 179835d6642cd5718a565869337b5420b29407a5
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160821'
 ---
+## Sobre o gerenciamento da equipe com {% data variables.product.prodname_emus %}
 
-## About team management with {% data variables.product.prodname_emus %}
+Com o {% data variables.product.prodname_emus %}, você pode gerenciar a associação à equipe e à organização na sua empresa por meio do IdP conectando as equipes do {% data variables.product.prodname_dotcom %} aos grupos de IdP. Quando conectar uma equipe de uma das organizações da sua empresa a um grupo do IdP as alterações nos integrantes do grupo do IdP serão refletidas na sua empresa automaticamente, reduzindo a necessidade de atualizações manuais e scripts personalizados. 
 
-With {% data variables.product.prodname_emus %}, you can manage team and organization membership within your enterprise through your IdP by connecting {% data variables.product.prodname_dotcom %} teams with IdP groups. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. 
-
-When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means.
+Quando uma alteração em um grupo de IdP ou uma nova conexão de equipe fizer com que o {% data variables.enterprise.prodname_managed_user %} ingresse em uma equipe de uma organização da qual já não faz parte, o {% data variables.enterprise.prodname_managed_user %} será adicionado à organização automaticamente. Ao desconectar um grupo de uma equipe, usuários que se tornaram integrantes da organização por da associação da equipe são removidos da organização se uma associação não lhes for atribuída na organização por outros meios.
 
 {% note %}
 
-**Note:** Organization owners can also add {% data variables.enterprise.prodname_managed_users %} to organizations manually, as long as the accounts have already been provisioned via SCIM.
+**Observação:** os proprietários da organização também podem adicionar {% data variables.enterprise.prodname_managed_users %} às organizações manualmente, desde que as contas já tenham sido provisionadas por meio do SCIM.
 
 {% endnote %}
 
-When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning.
+Quando o integrante do grupo mudar no seu IdP, este enviará uma solicitação de SCIM com alterações para {% data variables.product.prodname_dotcom_the_website %} de acordo com o cronograma determinado pelo seu IdP. Portanto, é possível que a alteração não seja imediata. Qualquer solicitação que altere a equipe de equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário.
 
-Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team.
+As quipes conectadas a grupos de IdP não podem ser equipes principais de outras equipes nem uma equipe secundária de outra equipe. Se a equipe que você deseja conectar a um grupo de IdP for uma equipe principal ou secundária recmendamos criar uma nova equipe ou remover a relação aninhada que faças da sua equipe uma equipe principal.
 
-To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
+Para gerenciar o acesso ao repositório para qualquer equipe do seu negócio, incluindo equipes conectadas a um grupo de IdP, você deverá fazer alterações em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como gerenciar o acesso da equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
 
-## Requirements for connecting IdP groups with teams
+## Requisitos para conectar grupos de IdP às equipes
 
-Before you can connect an IdP group with a team on {% data variables.product.prodname_dotcom %}, you must assign the group to the {% data variables.product.prodname_emu_idp_application %} application in your IdP. For more information, see "[About SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)."
+Para conectar um grupo de IdP a uma equipe no {% data variables.product.prodname_dotcom %}, você precisa atribuir o grupo ao aplicativo {% data variables.product.prodname_emu_idp_application %} no IdP. Para obter mais informações, confira "[Sobre o provisionamento do SCIM para o {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)".
 
-You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise.
+É possível conectar uma equipe da sua empresa a um grupo de IdP. Você pode atribuir o mesmo grupo do IdP a várias equipes na sua empresa.
 
-If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}.
+Se você estiver conectando uma equipe existente a um grupo de IdP, primeiro você deverá remover todos os integrantes que foram adicionados manualmente. Depois de conectar uma equipe da sua empresa a um grupo do IdP, o administrador do IdP deverá realizar as alterações na associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação da equipe em {% data variables.product.prodname_dotcom_the_website %}.
 
-## Creating a new team connected to an IdP group
+## Criando uma nova equipe conectada a um grupo de IdP
 
-Any member of an organization can create a new team and connect the team to an IdP group. 
+Qualquer integrante de uma organização pode criar uma nova equipe e conectar a equipe a um grupo de IdP. 
 
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.new_team %}
-{% data reusables.organizations.team_name %}
-{% data reusables.organizations.team_description %}
-1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
-{% data reusables.organizations.team_visibility %}
-{% data reusables.organizations.create_team %}
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %}
+1. Para conectar uma equipe, selecione o menu suspenso "Grupos de Fornecedores de Identidade" e clique na equipe que você deseja se conectar.
+    ![Menu suspenso usado para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %}
 
-## Managing the connection between an existing team and an IdP group
+## Gerenciando a conexão entre uma equipe existente e um grupo de IdP
 
-Organization owners and team maintainers can manage the existing connection between an IdP group and a team.
+Os proprietários da organização e mantenedores de equipe podem gerenciar a conexão existente entre um grupo de IdP e uma equipe.
 
 {% note %}
 
-**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)."
+**Observação**: para conectar uma equipe existente no {% data variables.product.prodname_dotcom_the_website %} a um grupo de IdP pela primeira vez, todos os membros da equipe no {% data variables.product.prodname_dotcom_the_website %} devem primeiro ser removidos. Para obter mais informações, confira "[Como remover membros da organização de uma equipe](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)".
 
 {% endnote %}
 
 {% data reusables.profile.access_profile %}
 
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.specific_team %}
-{% data reusables.organizations.team_settings %}
-1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
-1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
-1. Click **Save changes**.
+{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
+1. Opcionalmente, em "Grupo de Provedores de Identidade", à direita do grupo do IdP que deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. 
+    ![Cancelar a seleção de um grupo de IdP conectado da equipe do GitHub](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
+1. Para conectar um grupo de IdP, em "Grupo de Fornecedores de Identidade", selecione o menu suspenso e clique em um grupo de provedores de identidade da lista.
+    ![Menu suspenso usado para escolher o grupo de provedores de identidade](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+1. Clique em **Salvar alterações**.
 
-## Viewing IdP groups, group membership, and connected teams
+## Visualizando grupos de IdP, associações de grupo e equipes conectadas
 
-You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP.
+Você pode revisar uma lista de grupos de IdP, ver todas as equipes conectadas a um grupo de IdP, e ver a associação de cada grupo IdP no {% data variables.product.product_name %}. Você deve editar a associação de um grupo no seu IdP.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**.
-    ![Screenshot showing "Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png)
-2. To see the members and teams connected to an IdP group, click the group's name.
-    ![Screenshot showing list of IdP groups, the group name is highlighted](/assets/images/help/enterprises/select-idp-group.png)
-4. To view the teams connected to the IdP group, click **Teams**. 
-    ![Screenshot showing the "Teams" button](/assets/images/help/enterprises/idp-groups-team-switcher.png)
+1. Para revisar uma lista de grupos de IdP, na barra lateral esquerda, clique em {% octicon "key" aria-label="The key icon" %} **Provedor de Identidade**.
+    ![Captura de tela mostrando a guia "Provedor de identidade" na barra lateral da empresa](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png)
+2. Para ver os integrantes e equipes conectados a um grupo do IdP, clique no nome do grupo.
+    ![Captura de tela que mostra a lista de grupos de IdP; o nome do grupo está destacado](/assets/images/help/enterprises/select-idp-group.png)
+4. Para ver as equipes conectadas ao grupo de IdP, clique em **Equipes**. 
+    ![Captura de tela mostrando o botão "Equipes"](/assets/images/help/enterprises/idp-groups-team-switcher.png)

translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md

@@ -18,7 +18,7 @@ topics:
 
 ## Using the audit log API
 
-You can interact with the audit log using the GraphQL API or the REST API. 
+You can interact with the audit log using the GraphQL API or the REST API.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
 
 Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
 

translations/pt-BR/content/admin/overview/index.md

@@ -19,11 +19,11 @@ children:
   - /best-practices-for-enterprises
   - /creating-an-enterprise-account
   - /accessing-compliance-reports-for-your-enterprise
-ms.openlocfilehash: d936542993310333e314efcc9d5bb5689be00701
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f0322eef087f09b029051fc08ac61bc4e529d6dc
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147389840'
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163555'
 ---
 Para obter mais informações ou para comprar o {% data variables.product.prodname_enterprise %}, confira [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).

translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md

@@ -1,7 +1,7 @@
 ---
-title: Configuring the CodeQL workflow for compiled languages
+title: Configuração do fluxo de trabalho do CodeQL para linguagens compiladas
 shortTitle: Configure compiled languages
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.code-scanning.codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
+intro: 'Você pode configurar como o {% data variables.product.prodname_dotcom %} usa o {% data variables.code-scanning.codeql_workflow %} para examinar o código escrito nas linguagens compiladas quanto a vulnerabilidades e erros.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
 redirect_from:
@@ -25,107 +25,106 @@ topics:
   - C/C++
   - C#
   - Java
+ms.openlocfilehash: 91983e79a6381b4a38cbb1de4f6d7f228637b192
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161196'
 ---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
+## Sobre o {% data variables.code-scanning.codeql_workflow %} e as linguagens compiladas
 
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
+Você configurou {% data variables.product.prodname_dotcom %} para executar {% data variables.product.prodname_code_scanning %} para o seu repositório, adicionando um fluxo de trabalho de {% data variables.product.prodname_actions %} ao repositório. Para a {% data variables.product.prodname_code_scanning %} do {% data variables.product.prodname_codeql %}, você adiciona o {% data variables.code-scanning.codeql_workflow %}. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
 
-## About the {% data variables.code-scanning.codeql_workflow %} and compiled languages
+{% data reusables.code-scanning.edit-workflow %} Para obter informações gerais sobre como configurar a {% data variables.product.prodname_code_scanning %} e editar arquivos de fluxo de trabalho, confira "[Como configurar a {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" e "[Aprenda a usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.code-scanning.codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+##  Sobre a autobuild para {% data variables.product.prodname_codeql %}
 
-{% data reusables.code-scanning.edit-workflow %} 
-For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and  "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
-
-##  About autobuild for {% data variables.product.prodname_codeql %}
-
-{% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.   
-For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
+A {% data variables.product.prodname_code_scanning_capc %} funciona executando consultas em um ou mais bancos de dados. Cada banco de dados contém uma representação de todo o código em uma linguagem única no seu repositório.   
+Para as linguagens compiladas C/C++, C#,{% ifversion codeql-go-autobuild %} Go{% endif %} e Java, o processo de população desse banco de dados envolve a construção do código e a extração de dados. {% data reusables.code-scanning.analyze-go %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %}
 
-If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
+Se o fluxo de trabalho usar uma matriz `language`, `autobuild` tentará criar cada uma das linguagens compiladas listadas na matriz. Sem uma matriz, `autobuild` tentará criar a linguagem compilada compatível que tem mais arquivos de origem no repositório. Com exceção de Go, a análise de outras linguagens compatíveis no repositório irá falhar, a menos que você forneça comandos de criação explícitos.
 
 {% note %}
 
-{% ifversion ghae %}
-**Note**: {% data reusables.actions.self-hosted-runners-software %}
-{% else %}
-**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% ifversion ghae %} **Observação**: {% data reusables.actions.self-hosted-runners-software %} {% else %} **Observação**: caso você use executores auto-hospedados para o {% data variables.product.prodname_actions %}, talvez seja necessário instalar um software adicional para usar o processo `autobuild`. Além disso, se seu repositório precisar de uma versão específica de uma ferramenta de criação, talvez seja necessário instalá-lo manualmente. Para obter mais informações, confira "[Especificações para os executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
 {% endnote %}
 
 ### C/C++
 
-| Supported system type | System name |
+| Tipo de sistema compatível | Nome do sistema |
 |----|----|
-| Operating system | Windows, macOS, and Linux |
-| Build system | Windows: MSbuild and build scripts<br/>Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
+| Sistema operacional | Windows, macOS e Linux |
+| Sistema de criação | Windows: MSbuild e scripts de build<br/>Linux e macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild e scripts de build |
 
-The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
+O comportamento da etapa `autobuild` varia de acordo com o sistema operacional em que a extração é executada. No Windows, a etapa `autobuild` tenta fazer a detecção automática de um método de build adequado para C/C++ usando a seguinte abordagem:
 
-1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root.
-If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
+1. Invocar `MSBuild.exe` no arquivo de solução (`.sln`) ou de projeto (`.vcxproj`) mais próximo da raiz.
+Se `autobuild` detectar vários arquivos de solução ou de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará compilar todos eles.
+2. Invocar um script parecido com um script de build: _build.bat_, _build.cmd_ e _build.exe_ (nessa ordem).
 
-On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
+No Linux e no macOS, a etapa `autobuild` revisa os arquivos presentes no repositório para determinar o sistema de build usado:
 
-1. Look for a build system in the root directory.
-2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
-3. Run an appropriate command to configure the system. 
+1. Procure um sistema de criação no diretório-raiz.
+2. Se nenhum for encontrado, procure um diretório único nos subdiretórios com um sistema de criação para C/C++.
+3. Execute um comando apropriado para configurar o sistema. 
 
 ### C#
 
-| Supported system type | System name |
+| Tipo de sistema compatível | Nome do sistema |
 |----|----|
-| Operating system | Windows and Linux |
-| Build system | .NET and MSbuild, as well as build scripts |
+| Sistema operacional | Windows e Linux |
+| Sistema de criação | .NET, MSbuild e scripts de criação |
 
-The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
+O processo `autobuild` tenta fazer a detecção automática de um método de build adequado para C# usando a seguinte abordagem:
 
-1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
-2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root.
-If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
+1. Invocar `dotnet build` no arquivo de solução (`.sln`) ou de projeto (`.csproj`) mais próximo da raiz.
+2. Invocar `MSbuild` (Linux) ou `MSBuild.exe` (Windows) no arquivo de solução ou de projeto mais próximo da raiz.
+Se `autobuild` detectar vários arquivos de solução ou de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará compilar todos eles.
+3. Invocar um script parecido com um script de build: _build_ e _build.sh_ (nessa ordem, para o Linux) ou _build.bat_, _build.cmd_ e _build.exe_ (nessa ordem, para o Windows).
 
 {% ifversion codeql-go-autobuild %}
 
 ### Go
 
-| Supported system type | System name |
+| Tipo de sistema compatível | Nome do sistema |
 |----|----|
-| Operating system | Windows, macOS, and Linux |
-| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
+| Sistema operacional | Windows, macOS e Linux |
+| Sistema de criação | Módulos Go, `dep` e Glide, bem como scripts de build, incluindo Makefiles e scripts Ninja |
 
-The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
+O processo `autobuild` tenta fazer a detecção automática de uma forma adequada para instalar as dependências necessárias em um repositório Go antes de extrair todos os arquivos `.go`:
 
-1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed.
-2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies.
-3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
-4. Extract all Go code in the repository, similar to running `go build ./...`.
+1. Invoque `make`, `ninja`, `./build` ou `./build.sh` (nessa ordem) até que um desses comandos seja bem-sucedido e um próximo `go list ./...` também seja bem-sucedido, indicando que as dependências necessárias foram instaladas.
+2. Se nenhum desses comandos for bem-sucedido, procure `go.mod`, `Gopkg.toml` ou `glide.yaml` e execute `go get` (a menos que a cópia para a pasta Vendor esteja em uso), `dep ensure -v` ou `glide install`, respectivamente, para tentar instalar as dependências.
+3. Por fim, se os arquivos de configurações desses gerenciadores de dependência não forem encontrados, reorganize a estrutura de diretório do repositório adequada para adição a `GOPATH` e use `go get` para instalar as dependências. A estrutura de diretório é revertida para normal após a conclusão da extração.
+4. Extraia todo o código Go no repositório, semelhante à execução de `go build ./...`.
 
 {% endif %}
 
 ### Java
 
-| Supported system type | System name |
+| Tipo de sistema compatível | Nome do sistema |
 |----|----|
-| Operating system | Windows, macOS, and Linux (no restriction) |
-| Build system | Gradle, Maven and Ant |
+| Sistema operacional | Windows, macOS e Linux (sem restrição) |
+| Sistema de criação | Gradle, Maven e Ant |
 
-The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
+O processo `autobuild` tenta determinar o sistema de build para bases de código Java aplicando esta estratégia:
 
-1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
-2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
-3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
+1. Procurar um arquivo de criação no diretório-raiz. Verifique o arquivos do Gradle, do Maven e, em seguida, do Ant.
+2. Execute o primeiro arquivo de criação encontrado. Se os arquivos do Gradle e do Maven estiverem presentes, será usado o arquivo do Gradle.
+3. Caso contrário, procure arquivos de criação nos subdiretórios diretos do diretório-raiz. Se apenas um subdiretório contiver arquivos de criação, execute o primeiro arquivo identificado nesse subdiretório (usando a mesma preferência de 1). Se mais de um subdiretório conter arquivos de criação, relate um erro.
 
-## Adding build steps for a compiled language
+## Adicionar passos de criação a uma linguagem compilada
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
+{% data reusables.code-scanning.autobuild-add-build-steps %} Para obter informações sobre como editar o arquivo de fluxo de trabalho, confira "[Como configurar a {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)".
 
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process.
+Depois de remover a etapa `autobuild`, remova o comentário da etapa `run` e adicione comandos de build adequados ao seu repositório. A etapa `run` do fluxo de trabalho executa programas de linha de comando usando o shell do sistema operacional. Você pode modificar esses comandos e adicionar mais comandos para personalizar o processo de compilação.
 
 ``` yaml
 - run: |
@@ -133,9 +132,9 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
     make release
 ```
 
-For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+Para obter mais informações sobre a palavra-chave `run`, confira "[Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)".
 
-If your repository contains multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, and `autobuild` correctly builds C/C++ and C# but fails to build Java, you could use the following configuration in your workflow, after the `init` step. This specifies build steps for Java while still using `autobuild` for C/C++ and C#:
+Se o repositório contiver várias linguagens compiladas, você poderá especificar comandos de compilação específicos da linguagem. Por exemplo, se o repositório contiver C/C++, C# e Java e `autobuild` compilar corretamente C/C++ e C#, mas não compila Java, você poderá usar a configuração a seguir no seu fluxo de trabalho, após a etapa `init`. Isso especifica as etapas de compilação para Java enquanto ainda usa `autobuild` para C/C++ e C#:
 
 ```yaml
 - if: matrix.language == 'cpp' || matrix.language == 'csharp' 
@@ -149,8 +148,8 @@ If your repository contains multiple compiled languages, you can specify languag
     make release
 ```
 
-For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
+Para obter mais informações sobre o condicional `if`, confira "[Sintaxe de fluxo de trabalho do GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)".
 
-For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
+Para obter mais dicas e truques sobre por que o `autobuild` não compilará seu código, confira "[Solução de problemas de fluxo de trabalho do {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)".
 
-If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
+Se você adicionou etapas de criação manual para linguagens compiladas, mas o {% data variables.product.prodname_code_scanning %} ainda não está funcionando no seu repositório, entre em contato com {% data variables.contact.contact_support %}.

translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md

@@ -1,5 +1,5 @@
 ---
-title: Uploading a SARIF file to GitHub
+title: Fazer o upload de arquivo SARIF para o GitHub
 shortTitle: Upload a SARIF file
 intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}'
 permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.'
@@ -23,54 +23,57 @@ topics:
   - Repositories
   - CI
   - SARIF
+ms.openlocfilehash: 3def104e487f54e2c48d462d1dcfe8bab63c6fa3
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161155'
 ---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
+## Sobre os uploads de arquivos SARIF para {% data variables.product.prodname_code_scanning %}
 
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+O {% data variables.product.prodname_dotcom %} cria alertas de {% data variables.product.prodname_code_scanning %} em um repositório usando informações de arquivos de Formato Intercâmbio de Resultados de Análise Estática (SARIF). Os arquivos SARIF podem ser enviados para um repositório usando a API ou {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Como gerenciar alertas da {% data variables.product.prodname_code_scanning %} do seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
 
-## About SARIF file uploads for {% data variables.product.prodname_code_scanning %}
+Você pode gerar arquivos SARIF usando muitas ferramentas de teste de segurança de análise estática, incluindo {% data variables.product.prodname_codeql %}. Os resultados devem usar o SARIF versão 2.1.0. Para obter mais informações, confira "[Suporte do SARIF à {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)".
 
-{% data variables.product.prodname_dotcom %} creates {% data variables.product.prodname_code_scanning %} alerts in a repository using information from Static Analysis Results Interchange Format (SARIF) files. SARIF files can be uploaded to a repository using the API or {% data variables.product.prodname_actions %}. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+Carregue os resultados usando o {% data variables.product.prodname_actions %}, a API da {% data variables.product.prodname_code_scanning %},{% ifversion codeql-runner-supported %} o {% data variables.code-scanning.codeql_runner %},{% endif %} ou a {% data variables.product.prodname_codeql_cli %}. O melhor método de upload dependerá de como você gera o arquivo SARIF. Por exemplo, se você usar:
 
-You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
-
-You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API,{% ifversion codeql-runner-supported %} the {% data variables.code-scanning.codeql_runner %},{% endif %} or the {% data variables.product.prodname_codeql_cli %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
-
-- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
-- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
- - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% ifversion codeql-runner-supported %}
-- The {% data variables.code-scanning.codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %}
-- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
+- {% data variables.product.prodname_actions %} para executar a ação {% data variables.product.prodname_codeql %}, não haverá nenhuma ação adicional necessária. A ação {% data variables.product.prodname_codeql %} faz o upload do arquivo SARIF automaticamente quando ele conclui a análise.
+- O arquivo SARIF pode ser gerado a partir de uma ferramenta de análise compatível com o SARIF, que você executa no mesmo fluxo de trabalho de {% data variables.product.prodname_actions %} usado para fazer o upload do arquivo.
+ - A {% data variables.product.prodname_codeql_cli %} para executar a {% data variables.product.prodname_code_scanning %} no sistema de CI. Você pode usar a CLI para carregar resultados no {% data variables.product.prodname_dotcom %} (para obter mais informações, confira "[Como instalar a {% data variables.product.prodname_codeql_cli %} no sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% ifversion codeql-runner-supported %}
+- O {% data variables.code-scanning.codeql_runner %}, para executar a {% data variables.product.prodname_code_scanning %} no seu sistema de CI. Por padrão, o executor carrega automaticamente os resultados no {% data variables.product.prodname_dotcom %} após a conclusão. Se você bloquear o upload automático, quando estiver pronto para carregar os resultados, use o comando `upload` (para obter mais informações, confira "[Como executar o {% data variables.code-scanning.codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %}
+- Uma ferramenta que gera resultados como um artefato fora do repositório. Você pode usar a API da {% data variables.product.prodname_code_scanning %} para carregar o arquivo (para obter mais informações, confira "[Carregar uma análise como dados SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
 
-## Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
+## Fazer o upload uma análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_actions %}
 
-To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a  workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Para fazer com que {% data variables.product.prodname_actions %} faça um upload de um arquivo SARIF de terceiros para um repositório, você precisará de um fluxo de trabalho. Para obter mais informações, confira "[Aprenda a usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameters you'll use are:
+O fluxo de trabalho precisará usar a ação `upload-sarif`, que faz parte do repositório `github/codeql-action`. Ele tem parâmetros de entrada que você pode usar para configurar o upload. Os principais parâmetros de entrada que você vai usar são:
 
-- `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository.
-- `category` (optional), which assigns a category for results in the SARIF file. This enables you to analyze the same commit in multiple ways and review the results using the {% data variables.product.prodname_code_scanning %} views in {% data variables.product.prodname_dotcom %}. For example, you can analyze using multiple tools, and in mono-repos, you can analyze different slices of the repository based on the subset of changed files.
+- `sarif-file`, que configura o arquivo ou o diretório de arquivos SARIF a serem carregados. O diretório ou caminho do arquivo é relativo à raiz do repositório.
+- `category` (opcional), que atribui uma categoria para os resultados no arquivo SARIF. Isso permite que você analise o mesmo commit de várias maneiras e reveja os resultados usando as visualizações de {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_dotcom %}. Por exemplo, você pode analisar usando várias ferramentas, e nos monorrepositórios, você pode analisar diferentes porções do repositório com base no subconjunto de arquivos alterados.
 
-For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
+Para obter mais informações, confira a [ação `upload-sarif`](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
 
-The `upload-sarif` action can be configured to run when the `push` and `scheduled` event occur. For more information about {% data variables.product.prodname_actions %}  events, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+A ação `upload-sarif` pode ser configurada para ser executada quando os eventos `push` e `scheduled` ocorrerem. Para obter mais informações sobre os eventos do {% data variables.product.prodname_actions %}, confira "[Eventos que disparam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)."
+Se o arquivo SARIF não incluir `partialFingerprints`, a ação `upload-sarif` calculará o campo `partialFingerprints` para você e tentará evitar alertas duplicados. O {% data variables.product.prodname_dotcom %} só poderá criar `partialFingerprints` quando o repositório contiver o arquivo SARIF e o código-fonte usado na análise estática. Para obter mais informações sobre como evitar alertas duplicados, confira "[Sobre o suporte do SARIF para verificação de código](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)".
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### Example workflow for SARIF files generated outside of a repository
+### Exemplo de fluxo de trabalho para arquivos SARIF gerados fora de um repositório
 
-You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository.
+Você pode criar um novo fluxo de trabalho que faz o upload de arquivos SARIF após fazer o commit deles no seu repositório. Isso é útil quando o arquivo SARIF é gerado como um artefato fora do seu repositório.
 
-This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Este exemplo de fluxo de trabalho é executado sempre que os commits são carregados no repositório. A ação usa a propriedade `partialFingerprints` para determinar se as alterações ocorreram. Além de ser executado quando as confirmações são enviadas por push, o fluxo de trabalho é agendado para ser executado uma vez por semana. Para obter mais informações, confira "[Eventos que disparam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-This workflow uploads the `results.sarif` file located in the root of the repository. For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Esse fluxo de trabalho carrega o arquivo `results.sarif` localizado na raiz do repositório. Para obter mais informações sobre como editar um arquivo de fluxo de trabalho, confira "[Saiba como usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-Alternatively, you could modify this workflow to upload a directory of SARIF files. For example, you could place all SARIF files in a directory in the root of your repository called `sarif-output` and set the action's input parameter `sarif_file` to `sarif-output`. Note that if you upload a directory, each SARIF file must include a unique `runAutomationDetails.id` to define the category for the results. For more information, see "[`runAutomationDetails` object](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)."
+Como alternativa, você pode modificar este fluxo de trabalho para fazer upload de um diretório de arquivos SARIF. Por exemplo, você pode posicionar todos os arquivos SARIF em um diretório na raiz do seu repositório chamado `sarif-output` e definir o parâmetro de entrada `sarif_file` da ação como `sarif-output`. Observe que, se você carregar um diretório, cada arquivo SARIF precisará incluir uma `runAutomationDetails.id` exclusiva para definir a categoria para os resultados. Para obter mais informações, confira "[Objeto `runAutomationDetails`](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)".
 
 ```yaml
 name: "Upload SARIF"
@@ -105,13 +108,13 @@ jobs:
           category: my-analysis-tool
 ```
 
-### Example workflow that runs the ESLint analysis tool
+### Exemplo de fluxo de trabalho que executa a ferramenta de análise ESLint
 
-If you generate your third-party SARIF file as part of a continuous integration (CI) workflow, you can add the `upload-sarif` action as a step after running your CI tests. If you don't already have a CI workflow, you can create one using a {% data variables.product.prodname_actions %} template. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+Se você gerar o arquivo SARIF de terceiros como parte de um fluxo de trabalho de CI (integração contínua), poderá adicionar a ação `upload-sarif` como uma etapa depois de executar os testes de CI. Se você ainda não tiver um fluxo de trabalho de CI, você poderá criar um usando um modelo de {% data variables.product.prodname_actions %}. Para obter mais informações, confira o [guia de início rápido do "{% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Este exemplo de fluxo de trabalho é executado sempre que os commits são carregados no repositório. A ação usa a propriedade `partialFingerprints` para determinar se as alterações ocorreram. Além de ser executado quando as confirmações são enviadas por push, o fluxo de trabalho é agendado para ser executado uma vez por semana. Para obter mais informações, confira "[Eventos que disparam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+O fluxo de trabalho mostra um exemplo de execução da ferramenta de análise estática ESLint como uma etapa de um fluxo de trabalho. A etapa `Run ESLint` executa a ferramenta ESLint e gera o arquivo `results.sarif`. Em seguida, o fluxo de trabalho carrega o arquivo `results.sarif` no {% data variables.product.prodname_dotcom %} usando a ação `upload-sarif`. Para obter mais informações sobre como criar um arquivo de fluxo de trabalho, confira "[Introdução ao GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
 ```yaml
 name: "ESLint analysis"
@@ -147,9 +150,9 @@ jobs:
           sarif_file: results.sarif
 ```
 
-## Further reading
+## Leitura adicional
 
-- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"
-- "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
+- "[Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
+- "[Como ver o histórico do fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)"
+- "[Sobre a {% data variables.product.prodname_code_scanning %} do {% data variables.product.prodname_codeql %} no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"
+- "[Carregar uma análise como dados SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"

translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md

@@ -1,7 +1,7 @@
 ---
-title: Running CodeQL runner in your CI system
+title: Executando um executor de CodeQL no seu sistema de CI
 shortTitle: Run CodeQL runner
-intro: 'You can use the {% data variables.code-scanning.codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+intro: 'Use o {% data variables.code-scanning.codeql_runner %} para executar a {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em um sistema de integração contínua de terceiros.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
@@ -24,102 +24,102 @@ topics:
   - Integration
   - CI
   - SARIF
+ms.openlocfilehash: 7e60376ed165a3af2da7f000c37d326cb33ade99
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161091'
 ---
-
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% ifversion codeql-runner-supported %}
 
-{% data reusables.code-scanning.deprecation-codeql-runner %}
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About the {% data variables.code-scanning.codeql_runner %}
+## Sobre o {% data variables.code-scanning.codeql_runner %}
 
-The {% data variables.code-scanning.codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
+O {% data variables.code-scanning.codeql_runner %} é uma ferramenta que você pode usar para executar a {% data variables.product.prodname_code_scanning %} no código que está processando em um sistema de CI (integração contínua) de terceiros. {% data reusables.code-scanning.about-code-scanning %} Para obter informações, confira "[Sobre a {% data variables.product.prodname_code_scanning %} com o {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)".
 
-In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. 
+Em muitos casos, é mais fácil configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql_cli %} diretamente no seu sistema de CI. 
 
-Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+Como alternativa, você pode usar {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}. Para obter informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
 
-The {% data variables.code-scanning.codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
+O {% data variables.code-scanning.codeql_runner %} é uma ferramenta de linha de comando que executa a análise do {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Você adiciona o executor ao sistema de terceiros e chama o executor para analisar o código e carregar os resultados no {% data variables.product.product_name %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório.
 
 {% note %}
 
-**Note:**
-{% ifversion fpt or ghec %}
-* The {% data variables.code-scanning.codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+**Observação:** {% ifversion fpt or ghec %}
+* O {% data variables.code-scanning.codeql_runner %} usa a CLI do {% data variables.product.prodname_codeql %} para analisar o código e, portanto, tem as mesmas condições da licença. É grátis usar em repositórios públicos que são mantidos no {% data variables.product.prodname_dotcom_the_website %}, e disponíveis para uso em repositórios privados que são propriedade de clientes com uma licença do {% data variables.product.prodname_advanced_security %}. Para obter informações, confira "[Termos e condições do {% data variables.product.product_name %} {% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql/license)" e "[CLI do {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
 {% else %}
-* The {% data variables.code-scanning.codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
-{% endif %}
-{% ifversion ghae %}
-* The {% data variables.code-scanning.codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries.
-For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
-{% endif %}
-{% endnote %}
+* O {% data variables.code-scanning.codeql_runner %} está disponível para os clientes com uma licença do {% data variables.product.prodname_advanced_security %}.
+{% endif %} {% ifversion ghae %}
+* O {% data variables.code-scanning.codeql_runner %} não deve ser confundido com a CLI do {% data variables.product.prodname_codeql %}. A CLI de {% data variables.product.prodname_codeql %} é uma interface de linha de comando que permite que você crie bancos de dados de {% data variables.product.prodname_codeql %} para pesquisa de segurança e executar consultas de {% data variables.product.prodname_codeql %}.
+Para obter mais informações, confira "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)".
+{% endif %} {% endnote %}
 
-## Downloading the {% data variables.code-scanning.codeql_runner %}
+## Como baixar o {% data variables.code-scanning.codeql_runner %}
 
-You can download the {% data variables.code-scanning.codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+Baixe o {% data variables.code-scanning.codeql_runner %} em https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. Em alguns sistemas operacionais, talvez você precise alterar as permissões para o arquivo baixado antes de executá-lo.
 
-On Linux:
+No Linux:
 
 ```shell
 chmod +x codeql-runner-linux
 ```
 
-On macOS:
+No macOS:
 
 ```shell
 chmod +x codeql-runner-macos
 sudo xattr -d com.apple.quarantine codeql-runner-macos
 ```
 
-On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
+No Windows, o arquivo `codeql-runner-win.exe` geralmente não exige nenhuma alteração nas permissões.
 
-## Adding the {% data variables.code-scanning.codeql_runner %} to your CI system
+## Como adicionar o {% data variables.code-scanning.codeql_runner %} ao seu sistema de CI
 
-Once you download the {% data variables.code-scanning.codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example: 
+Depois de baixar o {% data variables.code-scanning.codeql_runner %} e verificar se ele pode ser executado, você deverá disponibilizar o executor para cada servidor de CI que pretende usar para a {% data variables.product.prodname_code_scanning %}. Por exemplo, você pode configurar cada servidor para que copie o executor de um local central interno. Como alternativa, você poderia usar a API REST para obter o executor diretamente do {% data variables.product.prodname_dotcom %}, por exemplo: 
 
 ```shell
 wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
-In addition to this, each CI server also needs:
+Além disso, cada servidor de CI também precisa:
 
-- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.code-scanning.codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
-- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.code-scanning.codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+- Um {% data variables.product.prodname_github_app %} ou um {% data variables.product.pat_generic %} para uso do {% data variables.code-scanning.codeql_runner %}. Você precisa usar um token de acesso com o escopo `repo` ou um {% data variables.product.prodname_github_app %} com a permissão de gravação em `security_events` e permissões de leitura em `metadata` e em `contents`. Para obter informações, confira "[Como criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Como criar um {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)".
+- Acesso ao pacote do {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.code-scanning.codeql_runner %}. Este pacote contém consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %} mais o CLI de {% data variables.product.prodname_codeql %}, que é usado internamente pelo executor. Para obter informações, confira "[CLI do {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
 
-The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são:
 
-1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.code-scanning.codeql_runner %} can download the bundle automatically.
-1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.code-scanning.codeql_runner %}.
+1. Permita que os servidores de CI acessem https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action para que o {% data variables.code-scanning.codeql_runner %} possa baixar o pacote automaticamente.
+1. Baixe/extraia manualmente o pacote, armazene-o com outros recursos centrais e use o sinalizador <nobr>`--codeql-path`</nobr> para especificar a localização do pacote em chamadas para inicializar o {% data variables.code-scanning.codeql_runner %}.
 
-## Calling the {% data variables.code-scanning.codeql_runner %}
+## Como chamar o {% data variables.code-scanning.codeql_runner %}
 
-You should call the {% data variables.code-scanning.codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+Você deve chamar o {% data variables.code-scanning.codeql_runner %} na localização de checkout do repositório que deseja analisar. Os dois comandos principais são:
 
-1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
-1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
+1. `init`, necessário para inicializar o executor e criar um banco de dados do {% data variables.product.prodname_codeql %} para cada linguagem a ser analisada. Estas bases de dados são preenchidas e analisadas por comandos subsequentes.
+1. `analyze`, necessário para preencher os bancos de dados do {% data variables.product.prodname_codeql %}, analisá-los e carregar os resultados no {% data variables.product.product_name %}.
 
-For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or {% data variables.product.pat_generic %} to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
+Para os dois comandos, você precisa especificar a URL do {% data variables.product.product_name %}, o *OWNER/NAME* do repositório e os {% data variables.product.prodname_github_apps %} ou o {% data variables.product.pat_generic %} a serem usados para autenticação. Você também precisa especificar o local do pacote do CodeQL, a menos que o servidor de CI tenha acesso para baixá-lo diretamente do repositório `github/codeql-action`.
 
-You can configure where the {% data variables.code-scanning.codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
+Configure a localização em que o {% data variables.code-scanning.codeql_runner %} armazena o pacote do CodeQL para análise futura em um servidor usando o sinalizador <nobr>`--tools-dir`</nobr> e a localização em que ele armazena os arquivos temporários durante a análise usando <nobr>`--temp-dir`</nobr>.
 
-To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
+Para ver a referência de linha de comando do executor, use o sinalizador `-h`. Por exemplo, para listar todos os comandos, execute `codeql-runner-OS -h`, ou para listar todos os sinalizadores disponíveis para o comando `init`, execute `codeql-runner-OS init -h` (em que `OS` varia de acordo com o executável que está sendo usado). Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)".
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### Basic example
+### Exemplo básico
 
-This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
+Este exemplo executa a análise do {% data variables.product.prodname_codeql %} em um servidor de CI do Linux para o repositório `octo-org/example-repo` hospedado em `{% data variables.command_line.git_url_example %}`. O processo é muito simples porque o repositório contém apenas linguagens que podem ser analisadas diretamente pelo {% data variables.product.prodname_codeql %}, sem ser criado (ou seja, Go, JavaScript, Python e TypeScript).
 
-In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
+Neste exemplo, o servidor tem acesso para baixar o pacote do {% data variables.product.prodname_codeql %} diretamente do repositório `github/codeql-action`, ou seja, não é necessário usar o sinalizador `--codeql-path`.
 
-1. Check out the repository to analyze.
-1. Move into the directory where the repository is checked out.
-1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+1. Confira o repositório a ser analisado.
+1. Mova para o diretório para o local onde o repositório está reservado.
+1. Inicialize o {% data variables.code-scanning.codeql_runner %} e crie bancos de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas.
 
     ```shell
     $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
@@ -131,13 +131,13 @@ In this example, the server has access to download the {% data variables.product
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
-### Compiled language example
+### Exemplo de linguagem compilada
 
-This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
+Este exemplo é semelhante ao exemplo anterior. No entanto, desta vez, o repositório tem o código em C/C++, C# ou Java. Para criar um banco de dados de {% data variables.product.prodname_codeql %} para essas linguagens, o CLI precisa monitorar a criação. No final do processo de inicialização, o executor informa o comando que você precisa configurar o ambiente antes de criar o código. Você precisa executar esse comando antes de chamar o processo normal de build de CI e executar o comando `analyze`.
 
-1. Check out the repository to analyze.
-1. Move into the directory where the repository is checked out.
-1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+1. Confira o repositório a ser analisado.
+1. Mova para o diretório para o local onde o repositório está reservado.
+1. Inicialize o {% data variables.code-scanning.codeql_runner %} e crie bancos de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas.
     ```shell
     $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
         --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
@@ -148,37 +148,37 @@ This example is similar to the previous example, however this time the repositor
       Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
       ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
     ```
-1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
+1. Obtenha o script gerado pela ação `init` para configurar o ambiente para monitorar o build. Observe o ponto e espaço principal no seguinte trecho do código.
 
     ```shell
     $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
     ```
 
-1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)."
+1. Crie o código. No macOS, você precisa adicionar a variável de ambiente `$CODEQL_RUNNER` como prefixo ao comando de build. Para obter mais informações, confira "[Solução de problemas do {% data variables.code-scanning.codeql_runner %} no sistema de CI](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)".
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
 {% note %}
 
-**Note:** If you use a containerized build, you need to run the {% data variables.code-scanning.codeql_runner %} in the container where your build task takes place.
+**Observação:** se você usar um build conteinerizado, precisará executar o {% data variables.code-scanning.codeql_runner %} no contêiner em que a tarefa de build ocorre.
 
 {% endnote %}
 
-## Further reading
+## Leitura adicional
 
-- "[Configuring {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
-- "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
+- "[Como configurar o {% data variables.code-scanning.codeql_runner %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[Solução de problemas do {% data variables.code-scanning.codeql_runner %} no seu sistema de CI](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
 
 {% else %}
 
-## About the {% data variables.code-scanning.codeql_runner %}
+## Sobre o {% data variables.code-scanning.codeql_runner %}
 
-The {% data variables.code-scanning.codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity.
+O {% data variables.code-scanning.codeql_runner %} foi preterido. A versão 2.7.6 da [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) tem paridade completa de recursos.
 
-For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
+Para obter informações sobre como migrar para a {% data variables.product.prodname_codeql_cli %}, confira "[Como migrar do executor do CodeQL para a CLI do CodeQL](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)".
 
-## Further reading
+## Leitura adicional
 
-- [CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) in the GitHub Blog
+- [Reprovação do executor do CodeQL](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) no blog do GitHub
 
 {% endif %}

translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md

@@ -463,7 +463,13 @@ jobs:
 
 ### Enable auto-merge on a pull request
 
-If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when any tests and approvals required by the branch protection rules are successfully met. For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+{% note %}
+
+**Note:** If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless all the required status checks pass. For more information, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+{% endnote %}
 
 You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`:
 

translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md

@@ -0,0 +1,44 @@
+---
+title: Configuring private vulnerability reporting for a repository
+intro: Owners and administrators of public repositories can allow security researchers to report vulnerabilities securely in the repository by enabling private vulnerability reporting.
+permissions: 'Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+miniTocMaxHeadingLevel: 3
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Configure private vulnerability reporting
+---
+
+{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
+
+## About privately reporting a security vulnerability
+
+Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+
+{% data reusables.security-advisory.private-vulnerability-reporting-overview %}
+
+For maintainers, the benefits of using private vulnerability reporting are: 
+- Less risk of being contacted publicly, or via undesired means.
+- Receive reports in the same platform you resolve them in for simplicity
+- The security researcher creates or at least initiates the advisory report on the behalf of maintainers.
+- Maintainers receive reports in the same platform as the one used to discuss and resolve the advisories.
+- Vulnerability less likely to be in the public eye.
+- The opportunity to discuss vulnerability details privately with security researchers and collaborate on the patch.
+
+## Enabling or disabling private vulnerability reporting for a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
+
+ ![Screenshot of the "Code security and analysis" page with the "Enable" button emphasized for private vulnerability reporting](/assets/images/help/security/private-vulnerability-reporting-enable-or-disable.png)
+
+When a maintainer enables private security reporting for their repository, security researchers will see a new button in the **Advisories** page of the repository. The security researcher can click this button to privately report a security vulnerability to the repository maintainer. 
+
+ ![Screenshot showing the "Report a vulnerability" button](/assets/images/help/security/report-a-vulnerability-button.png)
+   

translations/pt-BR/content/codespaces/overview.md

@@ -1,7 +1,7 @@
 ---
-title: GitHub Codespaces overview
+title: Visão geral do GitHub Codespaces
 shortTitle: Overview
-intro: 'This guide introduces {% data variables.product.prodname_github_codespaces %} and provides details on how it works and how to use it.'
+intro: 'Este guia apresenta o {% data variables.product.prodname_github_codespaces %} e fornece informações sobre como ele funciona e como usá-lo.'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /codespaces/codespaces-reference/about-codespaces
@@ -15,52 +15,57 @@ versions:
 type: overview
 topics:
   - Codespaces
+ms.openlocfilehash: a1618c86671bc5b06474c41803c6b34576a897aa
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160797'
 ---
+## O que é um codespace?
 
-## What is a codespace?
+Um codespace é um ambiente de desenvolvimento hospedado na nuvem. Você pode personalizar seu projeto para o {% data variables.product.prodname_github_codespaces %} fazendo commit dos [arquivos de configuração](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) no seu repositório (geralmente conhecido como configuração como código), o que cria uma configuração de codespace repetível para todos os usuários do projeto.
 
-A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project.
+Cada codespace é executado em uma máquina virtual hospedada por {% data variables.product.prodname_dotcom %}. Você pode escolher o tipo de computador que deseja usar, dependendo dos recursos necessários. Vários tipos de computadores estão disponíveis, começando com um processador de dois núcleos, 4 GB de RAM e 32 GB de armazenamento. 
 
-Each codespace runs on a virtual machine hosted by {% data variables.product.prodname_dotcom %}. You can choose the type of machine you want to use, depending on the resources you need. Various types of machine are available, starting with a 2-core processor, 4 GB of RAM, and 32 GB of storage. 
+Você pode se conectar aos seus codespaces por meio do navegador, por meio do {% data variables.product.prodname_vscode %}, do aplicativo JetBrains Gateway ou usando a {% data variables.product.prodname_cli %}.
 
-You can connect to your codespaces from your browser, from {% data variables.product.prodname_vscode %}, from the JetBrains Gateway application, or by using {% data variables.product.prodname_cli %}.
+![Um diagrama que mostra como os {% data variables.product.prodname_github_codespaces %} funcionam](/assets/images/help/codespaces/codespaces-diagram.png)
 
-![A diagram showing how {% data variables.product.prodname_github_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png)
+## Como usar o {% data variables.product.prodname_github_codespaces %}
 
-## Using {% data variables.product.prodname_github_codespaces %}
-
-To begin developing using cloud-based compute resources, you can create a codespace from a template or from any branch or commit in a repository. When you create a codespace from a template, you can start from a blank template or choose a template suitable for the work you're doing.
+Para começar o desenvolvimento usando recursos de computação baseados na nuvem, crie um codespace com base em um modelo ou em qualquer branch ou faça commit em um repositório. Ao criar um codespace com base em um modelo, você pode começar com um modelo em branco ou escolher um modelo adequado para o trabalho que está fazendo.
 
 {% data reusables.codespaces.links-to-get-started %}
 
-### Using codespaces owned by your personal account
+### Como usar codespaces pertencentes à sua conta pessoal
 
-All personal {% data variables.product.prodname_dotcom_the_website %} accounts have a monthly quota of free use of {% data variables.product.prodname_github_codespaces %} included in the Free or Pro plan. You can get started using {% data variables.product.prodname_github_codespaces %} on your personal account without changing any settings or providing payment details.
+Todas as contas pessoais do {% data variables.product.prodname_dotcom_the_website %} têm uma cota mensal de uso gratuito do {% data variables.product.prodname_github_codespaces %} incluída no plano Gratuito ou Pro. Comece a usar o {% data variables.product.prodname_github_codespaces %} na sua conta pessoal sem alterar nenhuma configuração ou fornecer detalhes de pagamento.
 
-You can create and use a codespace for any repository you can clone. You can also use a template to create codespaces that are not initially associated with a repository. If you create a codespace from an organization-owned repository, use of the codespace will either be charged to the organization (if the organization is configured for this), or to your personal account. Codespaces created from templates are always charged to your personal account. 
+Você pode criar e usar um codespace para qualquer repositório que possa clonar. Também pode usar um modelo para criar codespaces que não estão inicialmente associados a um repositório. Se você criar um codespace por meio de um repositório de propriedade da organização, o uso do codespace será cobrado para a organização (se a organização estiver configurada para isso) ou para sua conta pessoal. Os codespaces criados com base em modelos são sempre cobrados na sua conta pessoal. 
 
 {% data reusables.codespaces.codespaces-continue-by-paying %} 
 
-### Using organization-owned codespaces
+### Como usar codespaces de propriedade da organização
 
-Organization owners can enable use of {% data variables.product.prodname_github_codespaces %}, billable to the organization or enterprise account. This applies to codespaces created from repositories owned by the organization. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." You can set a spending limit for use of {% data variables.product.prodname_github_codespaces %} on your organization or enterprise account. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
+Os proprietários da organização podem habilitar o uso do {% data variables.product.prodname_github_codespaces %}, faturável para a organização ou para a conta corporativa. Isso se aplica aos codespaces criados com base em repositórios pertencentes à organização. Para obter mais informações, confira "[Como habilitar {% data variables.product.prodname_github_codespaces %} para sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)". Defina um limite de gastos para uso do {% data variables.product.prodname_github_codespaces %} na sua organização ou na sua conta corporativa. Para obter mais informações, confira "[Como gerenciar limites de gastos do {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)".
 
-If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." Codespaces that are billed to an organization, or its parent enterprise, are owned by the organization and can be deleted an organization owner. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)." 
+Se o uso de um codespace for cobrado para uma organização ou uma empresa, isso será mostrado quando o codespace for criado. Para obter mais informações, confira "[Como criar um codespace para um repositório](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)". Os codespaces que são cobrados para uma organização ou para a empresa-mãe pertencem à organização e podem ser excluídos por um proprietário da organização. Para obter mais informações, confira "[Como excluir um codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)". 
 
-### Customizing {% data variables.product.prodname_github_codespaces %}
+### Como personalizar o {% data variables.product.prodname_github_codespaces %}
 
-To customize the runtimes and tools in your codespace, you can create one or more dev container configurations for your repository. Adding dev container configurations to your repository allows you to define a choice of different development environments that are appropriate for the work people will do in your repository. 
+Para personalizar os runtimes e as ferramentas em seu codespace, você pode criar uma ou mais configurações de contêiner de desenvolvimento para seu repositório. A adição de configurações de contêiner de desenvolvimento ao seu repositório permite que você defina uma escolha de diferentes ambientes de desenvolvimento apropriados para o trabalho que as pessoas farão em seu repositório. 
 
-If you create a codespace from a repository without any dev container configurations, {% data variables.product.prodname_github_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. If you create a codespace from a template, you might start with some initial configuration on top of the default image. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+Se você criar um codespace por meio de um repositório sem nenhuma configuração de contêiner de desenvolvimento, o {% data variables.product.prodname_github_codespaces %} clonará seu repositório em um ambiente com a imagem de codespace padrão que inclui muitas ferramentas, linguagens e ambientes de execução. Se você criar um codespace com base em um modelo, poderá começar com uma configuração inicial baseada na imagem padrão. Para obter mais informações, confira "[Introdução aos contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)".
 
-You can personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository. You can use dotfiles to set shell aliases and preferences, or to install your personal preference of the tools you like to use. If you use {% data variables.product.prodname_github_codespaces %} in the browser, or in {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to give your codespace editor the same settings, keyboard shortcuts, snippets, and extensions that you have set up in your local installation of {% data variables.product.prodname_vscode %}. 
+Personalize aspectos do ambiente do codespace usando um repositório de [dotfiles](https://dotfiles.github.io/tutorials/) público. Use dotfiles para definir aliases e preferências de shell ou para instalar sua preferência pessoal das ferramentas que deseja usar. Se você usar o {% data variables.product.prodname_github_codespaces %} no navegador ou no {% data variables.product.prodname_vscode %}, use [a Sincronização de Configurações](https://code.visualstudio.com/docs/editor/settings-sync) para fornecer ao editor de codespace as configurações, os atalhos de teclado, as extensões e os snippets idênticos que você configurou na instalação local do {% data variables.product.prodname_vscode %}. 
 
-For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
+Para obter mais informações, confira "[Como personalizar seu codespace](/codespaces/customizing-your-codespace)".
 
-## Billing for {% data variables.product.prodname_codespaces %}
+## Cobrança do {% data variables.product.prodname_codespaces %}
 
-For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+Para obter informações sobre preços, armazenamento e uso dos {% data variables.product.prodname_github_codespaces %}, confira "[Sobre a cobrança dos {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)".
 
 {% data reusables.codespaces.codespaces-spending-limit-requirement %} 
 
-{% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
+{% data reusables.codespaces.codespaces-monthly-billing %} Para obter informações de como os proprietários de organizações e os gerentes de cobrança podem gerenciar o limite de gastos dod {% data variables.product.prodname_github_codespaces %} de uma organização, confira "[Como gerenciar o limite de gastos do {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)".

translations/pt-BR/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md

@@ -1,8 +1,8 @@
 ---
-title: Testing dev container configuration changes on a prebuild-enabled branch
+title: Testando alterações de configuração de contêiner de desenvolvimento em um branch pré-compilado habilitado
 shortTitle: Test dev container changes
 allowTitleToDifferFromFilename: true
-intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace.
+intro: 'Ao alterar a configuração do contêiner de desenvolvimento para um branch que está habilitado para pré-compilações, você deverá testar suas alterações em um codespace.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,22 +11,27 @@ topics:
   - Codespaces
   - Set up
 permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch.
+ms.openlocfilehash: 29b44d0fb0b3bb3211f0c204cc7e99e39ab89b79
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159297'
 ---
+Quaisquer alterações feitas na configuração do contêiner de desenvolvimento para uma ramificação habilitada para pré-compilação resultarão em uma atualização da configuração do codespace e da pré-compilação associada. Por isso, é importante testar tais alterações em um codespace de um branch de teste antes de fazer o commit de suas alterações em um branch do repositório que é ativamente usado. Isso garantirá que você não estará introduzindo alterações para a sua equipe.
 
-Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild. It’s therefore important to test such changes in a codespace from a test branch before committing your changes to a branch of your repository that's actively used. This will ensure you’re not introducing breaking changes for your team.
+Para obter mais informações, confira "[Introdução aos contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)".
 
-For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+## Testando alterações para a configuração do contêiner de desenvolvimento
 
-## Testing changes to the dev container configuration
-
-1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
-1. In the codespace, check out a test branch. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)."
-1. Make the required changes to the dev container configuration.
-1. Apply the changes by rebuilding the container. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
-1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild for that branch.
+1. Crie um código a partir do branch pré-compilado cujo contêiner de desenvolvimento você deseja alterar. Para obter mais informações, confira "[Como criar um codespace para um repositório](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)".
+1. No codespaec, confira um branch de teste. Para obter mais informações, confira "[Como usar o controle do código-fonte no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)".
+1. Faça as alterações necessárias na configuração do contêiner de desenvolvimento.
+1. Aplique as alterações recompilando o container. Para obter mais informações, confira "[Introdução aos contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)".
+1. Depois de tudo parecer bom, recomendamos também criar um novo codespace a partir de seu branch de teste para garantir que tudo está funcionando. Você pode então fazer commit de suas alterações no branch padrão do repositório ou em um branch de recurso ativo, acionando uma atualização da pré-compilação para esse branch.
 
    {% note %}
    
-   **Note**: Creating this codespace will take longer than usual because it will not be created from a prebuild.
+   **Observação**: a criação desse codespace levará mais tempo do que o normal porque ele não será criado com base em um pré-build.
    
    {% endnote %}

translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md

@@ -1,6 +1,6 @@
 ---
-title: The github.dev web-based editor
-intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.'
+title: O editor github.dev baseado na web
+intro: 'Use o github.dev {% data variables.product.prodname_serverless %} do seu repositório ou faça uma solicitação de pull para criar e confirmar as alterações.'
 versions:
   feature: githubdev-editor
 type: how_to
@@ -12,104 +12,108 @@ topics:
 shortTitle: Web-based editor
 redirect_from:
   - /codespaces/developing-in-codespaces/web-based-editor
+ms.openlocfilehash: d1c21f3e75ecc4fec282c9156943c137287d203c
+ms.sourcegitcommit: caab4edbbeedf23e9062e48a67c35224772b6efa
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160474'
 ---
-
 {% note %}
 
-**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/general).
+**Observação:** atualmente, o github.dev {% data variables.product.prodname_serverless %} está em versão prévia beta. Envie comentários [em nossas Discussões](https://github.com/community/community/discussions/categories/general).
 
 {% endnote %}
 
-## About the {% data variables.product.prodname_serverless %}
+## Sobre o {% data variables.product.prodname_serverless %}
 
-The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor.
+O {% data variables.product.prodname_serverless %} introduz uma experiência leve de edição, que é executada inteiramente no seu navegador. Com o {% data variables.product.prodname_serverless %}, você pode navegar por arquivos e repositórios de código-fonte do {% data variables.product.prodname_dotcom %}, bem como efetuar e fazer comite das alterações de código. É possível abrir qualquer repositório, bifurcação ou pull request no editor.
 
-The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}.
+O {% data variables.product.prodname_serverless %} está disponível para todos gratuitamente em {% data variables.product.prodname_dotcom_the_website %}.
 
-The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+O {% data variables.product.prodname_serverless %} fornece muitos dos benefícios de {% data variables.product.prodname_vscode %}, como pesquisa, destaque de sintaxe e uma visão de controle de origem. Você também pode usar Sincronização de Configurações para compartilhar suas próprias configurações do {% data variables.product.prodname_vscode_shortname %} com o editor. Para obter mais informações, consulte "[Sincronização de Configurações](https://code.visualstudio.com/docs/editor/settings-sync)" na documentação do {% data variables.product.prodname_vscode_shortname %}.
 
-The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
+O {% data variables.product.prodname_serverless %} é executado inteiramente no sandbox do seu navegador. O editor não clona o repositório, mas usa a [extensão Repositórios do GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) para executar a maior parte da funcionalidade que você usará. Seu trabalho é salvo no armazenamento local do navegador até que você faça commit dele. Você deve fazer commit das alterações regularmente para garantir que estejam sempre acessíveis.
 
-You must be signed in to use the web-based editor.
+Você precisa estar conectado para usar o editor baseado na Web.
 
-## Opening the {% data variables.product.prodname_serverless %}
+## Abrindo o {% data variables.product.prodname_serverless %}
 
-You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
+Você pode abrir qualquer repositório de {% data variables.product.prodname_dotcom %} em {% data variables.product.prodname_serverless %} em qualquer uma das seguintes maneiras:
 
-- To open the repository in the same browser tab, press <kbd>.</kbd> while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
+- Para abrir o repositório na mesma guia do navegador, pressione <kbd>.</kbd> enquanto navega em qualquer repositório ou solicitação de pull no {% data variables.product.prodname_dotcom %}.
  
-  To open the repository in a new browser tab, press <kbd>></kbd>.
+  Para abrir o repositório em uma nova guia do navegador, pressione <kbd>></kbd>.
 
-- Change the URL from "github.com" to "github.dev".
-- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
+- Alterando a URL de "github.com" para "github.dev".
+- Ao exibir um arquivo, use o menu suspenso ao lado de {% octicon "pencil" aria-label="The edit icon" %} e selecione **Abrir no github.dev**.
 
-  ![Edit file button dropdown menu](/assets/images/help/repository/edit-file-edit-dropdown.png)
+  ![Menu suspenso do botão Editar arquivo](/assets/images/help/repository/edit-file-edit-dropdown.png)
 
-## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %}
+## {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_serverless %}
 
-Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_github_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case.
+Tanto o {% data variables.product.prodname_serverless %} quanto o {% data variables.product.prodname_github_codespaces %} permitem que você edite seu código diretamente do seu repositório. No entanto, ambos têm benefícios ligeiramente diferentes, dependendo da sua utilização.
 
 || {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_github_codespaces %}|
 |-|----------------|---------|
-| **Cost** | Free.      | Free monthly quota of usage for personal accounts. For information on pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)."|
-| **Availability** | Available to everyone on GitHub.com. | Available to everyone on GitHub.com. |
-| **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." |
-| **Compute**  | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With  {%  data variables.product.prodname_github_codespaces %}, you get the power of a dedicated VM on which you can run and debug your application.|
-| **Terminal access** | None. | {% data variables.product.prodname_github_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.|
-| **Extensions**  | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With {% data variables.product.prodname_github_codespaces %}, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.|
+| **Custo** | Livre.      | Cota mensal gratuita de uso para contas pessoais. Para obter mais informações sobre preços, confira "[Sobre a cobrança dos {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)".|
+| **Disponibilidade** | Disponível para todos no GitHub.com. | Disponível para todos no GitHub.com. |
+| **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. | Quando você cria ou retoma 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, confira "[Como criar um codespace para um repositório](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)". |
+| **Computação**  | Não há nenhum computador associado. Portanto você não conseguirá criar e executar o seu código ou usar o terminal integrado. | Com o {%  data variables.product.prodname_github_codespaces %}, você usufrui da alta eficiência de uma VM dedicada na qual pode executar e depurar seu aplicativo.|
+| **Acesso ao terminal** | Nenhum. | O {% data variables.product.prodname_github_codespaces %} fornece um conjunto comum de ferramentas por padrão, o que significa que você pode usar o Terminal exatamente como você faria no 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, confira "[Como usar extensões](#using-extensions)".| Com os {% data variables.product.prodname_github_codespaces %}, você pode usar a maioria das extensões do {% data variables.product.prodname_vscode_marketplace %}.|
 
-### Continue working on {% data variables.product.prodname_codespaces %}
+### Continue trabalhando nos {% data variables.product.prodname_codespaces %}
 
-You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace. If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}.
+Você pode iniciar o fluxo de trabalho no {% data variables.product.prodname_serverless %} e continuar trabalhando em um codespace. Se você tentar acessar a janela ou terminal Executar e Depurarl, você receberá uma mensagem de que eles não estão disponíveis em {% data variables.product.prodname_serverless %}.
 
-To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes.
+Para continuar seu trabalho em um codespace, clique em **Continuar Trabalhando em…** e selecione **Criar Codespace** para criar um codespace no branch atual. Antes de selecionar esta opção, você precisa fazer commit de quaisquer alterações.
 
-![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png)
+![Captura de tela que mostra o botão "Continuar Trabalhando" na interface do usuário](/assets/images/help/codespaces/codespaces-continue-working.png)
 
-## Using source control
+## Usando controle de origem
 
-When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+Ao usar o {% data variables.product.prodname_serverless %}, todas as ações são gerenciadas por meio da Visualização de Controle de Origem, localizado na Barra de Atividades do lado esquerdo. Para obter mais informações sobre a Exibição de Controle do Código-Fonte, consulte "[Controle de versão](https://code.visualstudio.com/docs/editor/versioncontrol)" na documentação do {% data variables.product.prodname_vscode_shortname %}.
 
-Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+Como o editor da web usa a extensão dos repositórios do GitHub para melhorar suas funcionalidades, você pode alternar entre branches sem precisar ocultar alterações. Para obter mais informações, consulte "[Repositórios do GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" na documentação do {% data variables.product.prodname_vscode_shortname %}.
 
-### Create a new branch
+### Criar uma nova ramificação
 
-{% data reusables.codespaces.create-or-switch-branch %}
-  Any uncommitted changes you have made in your old branch will be available on your new branch.
+{% data reusables.codespaces.create-or-switch-branch %} Todas as alterações sem commit feitas no branch antigo ficarão disponíveis no novo branch.
 
-### Commit your changes
+### Confirmar as alterações
 
 {% data reusables.codespaces.source-control-commit-changes %} 
-5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}.
-### Create a pull request
+5. Depois de ter feito as commit das suas alterações, elas serão automaticamente enviadas para o seu branch em {% data variables.product.prodname_dotcom %}.
+### Criar uma solicitação de pull
 
 {% data reusables.codespaces.source-control-pull-request %}
 
-### Working with an existing pull request
+### Trabalhando com um pull request existente
 
-You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request.
+Você pode usar o {% data variables.product.prodname_serverless %} para trabalhar com um pull request existente.
 
-1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}.
-2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}.
-3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes.
+1. Acesse o pull request que você gostaria de abrir em {% data variables.product.prodname_serverless %}.
+2. Pressione `.` para abrir a solicitação de pull no {% data variables.product.prodname_serverless %}.
+3. Depois de fazer alterações, faça commit delas usando as etapas descritas em [Fazer commit das alterações](#commit-your-changes). As suas alterações serão registradas diretamente no branch. Não é necessário fazer push das alterações.
 
-## Using extensions
+## Como usar extensões
 
-The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+O {% data variables.product.prodname_serverless %} é compatível com as extensões do {% data variables.product.prodname_vscode_shortname %} que foram especificamente criadas ou atualizadas para serem executadas na Web. Essas extensões são conhecidas como "extensões da web". Para saber como criar uma extensão da Web ou atualizar sua extensão existente para trabalhar na Web, consulte "[Extensões da Web](https://code.visualstudio.com/api/extension-guides/web-extensions)" na documentação do {% data variables.product.prodname_vscode_shortname %}.
 
-Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+As extensões que podem ser executadas no {% data variables.product.prodname_serverless %} aparecerão na vista de Extensões e poderão ser instaladas. Se você usar a Sincronização de Configurações, todas as extensões compatíveis também são instaladas automaticamente. Para obter mais informações, consulte "[Sincronização de Configurações](https://code.visualstudio.com/docs/editor/settings-sync)" na documentação do {% data variables.product.prodname_vscode_shortname %}.
 
 
-## Troubleshooting
+## Solução de problemas
 
-If you have issues opening the {% data variables.product.prodname_serverless %}, try the following:
+Se você tiver problemas ao abrir {% data variables.product.prodname_serverless %}, tente o seguinte:
 
-- Make sure you are signed in to {% data variables.product.prodname_dotcom %}.
-- Disable any ad blockers.
-- Use a non-incognito window in your browser to open the {% data variables.product.prodname_serverless %}.
+- Verifique se você está conectado a {% data variables.product.prodname_dotcom %}.
+- Desabilita qualquer bloqueador de anúncios.
+- Use uma janela não anônima no seu navegador para abrir o {% data variables.product.prodname_serverless %}.
 
-### Known limitations
+### Limitações conhecidas
 
-- The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
-- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation.
-- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
+- O {% data variables.product.prodname_serverless %} atualmente é compatível com o Chrome (e vários outros navegadores baseados no Chromium), Edge, Firefox e Safari. Recomendamos que você use as versões mais recentes desses navegadores.
+- Algumas teclas de atalho podem não funcionar, dependendo do navegador que você estiver usando. Essas limitações de associação de teclas são documentadas na seção "[Limitações e adaptações conhecidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" da documentação do {% data variables.product.prodname_vscode_shortname %}.
+- Talvez o `.` não funcione para abrir o {% data variables.product.prodname_serverless %} de acordo com o layout local do teclado. Nesse caso, você pode abrir qualquer repositório do {% data variables.product.prodname_dotcom %} no {% data variables.product.prodname_serverless %} alterando a URL de `github.com` para `github.dev`.

translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md

@@ -1,6 +1,6 @@
 ---
-title: Bloquear usuários da organização
-intro: Os proprietários e moderadores da organização podem impedir que qualquer pessoa que não seja membro da organização colabore nos repositórios da organização.
+title: Blocking a user from your organization
+intro: Organization owners and moderators can block anyone who is not a member of the organization from collaborating on the organization's repositories.
 redirect_from:
   - /articles/blocking-a-user-from-your-organization
   - /github/building-a-strong-community/blocking-a-user-from-your-organization
@@ -10,71 +10,68 @@ versions:
 topics:
   - Community
 shortTitle: Block from your org
-ms.openlocfilehash: 3264bb71f157c2ec34f42b859857eed4253379f3
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145084124'
 ---
-Você pode bloquear não membros de dentro das configurações da sua organização ou de um comentário específico feito por um usuário. Ao bloquear um usuário em um comentário, você pode optar por enviar ao usuário uma notificação explicando que ele foi bloqueado e por quê. Caso contrário, o usuário não será diretamente notificado que você o bloqueou. Os usuários bloqueados ainda podem excluir o conteúdo existente.
 
-Ao bloquear um usuário, você pode optar por bloqueá-lo indefinidamente ou por um período específico. Se você bloquear alguém por um período específico, ele será automaticamente desbloqueado após o término desse período. Se você bloquear alguém indefinidamente, será possível desbloqueá-lo manualmente a qualquer momento. Para obter mais informações, consulte "[Como bloquear um usuário da sua organização](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)".
+You can block non-members from within your organization's settings or from a specific comment made by a user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
+
+{% data reusables.organizations.blocking-a-user %}
 
 {% tip %}
 
-**Dica:** se você estiver bloqueando um usuário por causa de uma conversa acalorada, considere a possibilidade de bloquear a conversa para que apenas os colaboradores possam adicionar comentários a ela. Para obter mais informações, confira "[Como bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)".
+**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
 
 {% endtip %}
 
-No momento que você bloqueia um usuário da organização:
-- O usuário para de inspecionar os repositórios da sua organização
-- As estrelas e atribuições de problema do usuário são removidas dos repositórios
-- Os votos do usuário nas discussões ou comentários nos repositórios da sua organização são excluídos
-- O usuário é removido como um colaborador dos repositórios da organização
-- As contribuições do usuário para os repositórios da sua organização não são mais contabilizadas como contribuições para eles
-- Quaisquer convites de repositório ou organização pendentes para o usuário bloqueado são cancelados
+At the time that you block a user from your organization:
+- The user stops watching your organization's repositories
+- The user's stars and issue assignments are removed from your repositories
+- The user's votes on discussions or comments in your organization's repositories are deleted
+- The user is removed as a collaborator on your organization's repositories
+- The user's contributions to your organization's repositories are no longer counted as contributions for them
+- Any pending repository or organization invitations to the blocked user are cancelled
 
-Depois que você bloqueia um usuário na sua organização, ele não pode:
-- Fazer referência cruzada de repositórios da organização nos comentários
-- Bifurque, inspecione, fixe ou favorite os repositórios da sua organização
+After you've blocked a user from your organization, they cannot:
+- Cross-reference your organization's repositories in comments
+- Fork, watch, pin, or star your organization's repositories
 
-Nos repositórios da sua organização, os usuários bloqueados também não podem:
-- Criar problemas
-- Envie, feche ou mescle pull requests
-- Fazer comentários sobre problemas, pull request ou commits
-- Adicionar nem editar páginas wiki
+In your organization's repositories, blocked users also cannot:
+- Open issues
+- Send, close, or merge pull requests
+- Comment on issues, pull requests, or commits
+- Add or edit wiki pages
 
-## Bloquear um usuário em um comentário
+## Blocking a user in a comment
 
-1. Navegue até o comentário cujo autor você deseja bloquear.
-2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e clique em **Bloquear usuário**.
-![O ícone horizontal kebab e menu de moderação de comentários mostrando a opção bloquear usuário](/assets/images/help/repository/comment-menu-block-user.png)
-3. Se quiser configurar um limite de tempo para o bloqueio, use o menu suspenso Block user (Bloquear usuário) e selecione o período pelo qual deseja bloquear o usuário.
-![Limite de tempo de bloqueio no menu suspenso bloquear usuário](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
-4. Se quiser ocultar todos os comentários que o usuário fez na organização, selecione **Ocultar os comentários deste usuário** e escolha um motivo.
-![Enviar uma notificação no menu suspenso bloquear usuário](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
-5. Se quiser notificar o usuário sobre o motivo pelo qual ele está sendo bloqueado, selecione **Enviar uma notificação a este usuário**.
-![Enviar uma notificação no menu suspenso bloquear usuário](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
-6. Para bloquear o usuário, clique em **Bloquear usuário da organização** ou **Bloquear usuário da organização e enviar mensagem**.
-![Botão Bloquear usuário](/assets/images/help/organizations/org-block-user-button-in-comment.png)
+1. Navigate to the comment whose author you would like to block.
+2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block user**.
+![The horizontal kebab icon and comment moderation menu showing the block user option](/assets/images/help/repository/comment-menu-block-user.png)
+3. If you'd like to set a time limit for the block, use the Block user drop-down menu, and select the amount of time you'd like to block the user.
+![Block time limit in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
+4. If you'd like to hide all of the comments the user has made in the organization, select **Hide this user's comments** and choose a reason.
+![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
+5. If you'd like to notify the user why they're being blocked, select **Send a notification to this user**.
+![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
+6. To block the user, click **Block user from organization** or **Block user from organization and send message**.
+![Block user button](/assets/images/help/organizations/org-block-user-button-in-comment.png)
 
-## Bloquear um usuário nas configurações da organização
+## Blocking a user in the organization settings
 
-1. Para bloquear um membro da organização, primeiro [remova o usuário](/articles/removing-a-member-from-your-organization) da organização.
+1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
 
-{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.block_users %}
-6. Em "Block a user" (Bloquear um usuário), digite o nome de usuário que deseja bloquear.
-![Campo Nome de usuário](/assets/images/help/organizations/org-block-username-field.png)
-7. Se quiser configurar um limite de tempo para o bloqueio, use o menu suspenso Block options (Opções de bloqueio) e selecione o período pelo qual deseja bloquear o usuário.
-![Menu suspenso Opções de bloqueio](/assets/images/help/organizations/org-block-options-menu.png)
-8. Clique em **Bloquear usuário**.
-![Botão Bloquear](/assets/images/help/organizations/org-block-user-button.png)
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.block_users %}
+6. Under "Block a user", type the username of the user you'd like to block.
+![Username field](/assets/images/help/organizations/org-block-username-field.png)
+7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user.
+![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png)
+8. Click **Block user**.
+![Block button](/assets/images/help/organizations/org-block-user-button.png)
 
-## Leitura adicional
+## Further reading
 
-- [/viewing-users-who-are-blocked-from-your-organization](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)
-- "[Como desbloquear um usuário da sua organização](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
-- [/blocking-a-user-from-your-personal-account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)
-- "[Como desbloquear um usuário da sua conta pessoal](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
-- "[Como denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Viewing users who are blocked from your organization](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)"
+- "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
+- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
+- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
+- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"

translations/pt-BR/content/copilot/overview-of-github-copilot/about-github-copilot.md

@@ -1,41 +1,46 @@
 ---
-title: About GitHub Copilot
-intro: '{% data variables.product.prodname_copilot %} can help you code by offering autocomplete-style suggestions. You can learn what to consider while using {% data variables.product.prodname_copilot %}, and how {% data variables.product.prodname_copilot %} works.'
+title: Sobre o GitHub Copilot
+intro: 'O {% data variables.product.prodname_copilot %} pode ajudar você a criar códigos oferecendo sugestões de preenchimento automático. Saiba o que considerar ao usar o {% data variables.product.prodname_copilot %} e como o {% data variables.product.prodname_copilot %} funciona.'
 versions:
   feature: copilot
 topics:
   - Copilot
 shortTitle: About GitHub Copilot
+ms.openlocfilehash: dd4538cb4cf6fc9dd84bb3f0d05bf8a85559d5ec
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160637'
 ---
+## Sobre o {% data variables.product.prodname_copilot %}
 
-## About {% data variables.product.prodname_copilot %}
+O {% data variables.product.prodname_copilot %} é um programador de pares de IA que oferece sugestões de preenchimento automático conforme você codifica. Você pode receber sugestões do {% data variables.product.prodname_copilot %} ao começar a escrever o código que deseja usar ou um comentário em linguagem natural descrevendo o que deseja que o código faça. O {% data variables.product.prodname_copilot %} analisa o contexto no arquivo que você está editando, bem como arquivos relacionados, e oferece sugestões de dentro do editor de texto. O {% data variables.product.prodname_copilot %} é da plataforma OpenAI Codex, um sistema de IA criado pelo OpenAI.
 
-{% data variables.product.prodname_copilot %} is an AI pair programmer that offers autocomplete-style suggestions as you code. You can receive suggestions from {% data variables.product.prodname_copilot %} either by starting to write the code you want to use, or by writing a natural language comment describing what you want the code to do. {% data variables.product.prodname_copilot %} analyzes the context in the file you are editing, as well as related files, and offers suggestions from within your text editor. {% data variables.product.prodname_copilot %} is powered by OpenAI Codex, a new AI system created by OpenAI.
+O {% data variables.product.prodname_copilot %} é treinado em todas as linguagens que são exibidas nos repositórios públicos. Para cada linguagem, a qualidade das sugestões recebidas pode depender do volume e da diversidade de dados de treinamento para essa linguagem. Por exemplo, o JavaScript é bem representado nos repositórios públicos e é uma das linguagens com melhor suporte do {% data variables.product.prodname_copilot %}. As linguagens com menos representação nos repositórios públicos podem produzir sugestões menos robustas e um número menor de sugestões.
 
-{% data variables.product.prodname_copilot %} is trained on all languages that appear in public repositories. For each language, the quality of suggestions you receive may depend on the volume and diversity of training data for that language. For example, JavaScript is well-represented in public repositories and is one of {% data variables.product.prodname_copilot %}'s best supported languages. Languages with less representation in public repositories may produce fewer or less robust suggestions.
+O {% data variables.product.prodname_copilot %} está disponível como uma extensão no Visual Studio Code, no Visual Studio, no Neovim e no pacote de IDEs da JetBrains. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot)".
 
-{% data variables.product.prodname_copilot %} is available as an extension in Visual Studio Code, Visual Studio, Neovim and the JetBrains suite of IDEs. For more information, see "[Getting started with {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot)."
+## Como usar o {% data variables.product.prodname_copilot %}
 
-## Using {% data variables.product.prodname_copilot %}
+Veja exemplos reais do {% data variables.product.prodname_copilot %} em ação. Para obter mais informações, confira o site do [{% data variables.product.prodname_copilot %}](https://copilot.github.com/). 
 
-You can see real-world examples of {% data variables.product.prodname_copilot %} in action. For more information, see the [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) website. 
+O GitHub Copilot oferece sugestões de um modelo que o OpenAI criou com base em bilhões de linhas de código aberto. Como resultado, o conjunto de treinamento do {% data variables.product.prodname_copilot %} pode conter padrões de codificação não seguros, bugs ou referências a APIs desatualizadas ou gírias. Quando o {% data variables.product.prodname_copilot %} gera sugestões com base nesses dados de treinamento, essas sugestões também podem conter padrões indesejáveis. 
 
-GitHub Copilot offers suggestions from a model that OpenAI built from billions of lines of open source code. As a result, the training set for {% data variables.product.prodname_copilot %} may contain insecure coding patterns, bugs, or references to outdated APIs or idioms. When {% data variables.product.prodname_copilot %} produces suggestions based on this training data, those suggestions may also contain undesirable patterns. 
+Você é responsável por garantir a segurança e a qualidade do código. Recomendamos que você tome as mesmas precauções ao usar o código gerado pelo {% data variables.product.prodname_copilot %} que tomaria ao usar qualquer código escrito por outra pessoa. Essas precauções incluem testes rigorosos, verificação de IP e acompanhamento de vulnerabilidades de segurança. O {% data variables.product.company_short %} oferece vários recursos que ajudam a monitorar e aprimorar a qualidade do código, como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_codeql %} e {% data variables.product.prodname_code_scanning %}. Todos esses recursos são gratuitos para serem usados em repositórios públicos. Para obter mais informações, confira "[Noções básicas sobre o {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)" e "[Recursos de segurança do {% data variables.product.company_short %}](/code-security/getting-started/github-security-features)".
 
-You are responsible for ensuring the security and quality of your code. We recommend you take the same precautions when using code generated by {% data variables.product.prodname_copilot %} that you would when using any code you didn't write yourself. These precautions include rigorous testing, IP scanning, and tracking for security vulnerabilities. {% data variables.product.company_short %} provides a number of features to help you monitor and improve code quality, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_codeql %} and {% data variables.product.prodname_code_scanning %}. All these features are free to use in public repositories. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)" and "[{% data variables.product.company_short %} security features](/code-security/getting-started/github-security-features)."
-
-{% data variables.product.prodname_copilot %} uses filters to block offensive words in the prompts and avoid producing suggestions in sensitive contexts. We are committed to constantly improving the filter system to more intelligently detect and remove offensive suggestions generated by {% data variables.product.prodname_copilot %}, including biased, discriminatory, or abusive outputs. If you see an offensive suggestion generated by {% data variables.product.prodname_copilot %}, please report the suggestion directly to copilot-safety@github.com so that we can improve our safeguards. 
+O {% data variables.product.prodname_copilot %} usa filtros para bloquear palavras ofensivas nos prompts e evitar a geração de sugestões em contextos confidenciais. Estamos comprometidos em sempre aprimorar o sistema de filtro para detectar e remover com mais inteligência as sugestões ofensivas geradas pelo {% data variables.product.prodname_copilot %}, incluindo saídas tendenciosas, discriminatórias ou abusivas. Se você encontrar uma sugestão ofensiva gerada pelo {% data variables.product.prodname_copilot %}, relate-a diretamente a copilot-safety@github.com, para que possamos aprimorar as proteções. 
 
 {% data reusables.copilot.emus-cannot-use-copilot %}
 
-## About billing for {% data variables.product.prodname_copilot %}
+## Sobre a cobrança do {% data variables.product.prodname_copilot %}
 
-{% data variables.product.prodname_copilot %} is a paid feature, requiring a monthly or yearly subscription. Verified students, teachers, and maintainers of popular open source projects on {% data variables.product.prodname_dotcom %} are eligible to use {% data variables.product.prodname_copilot %} for free. If you meet the criteria for a free {% data variables.product.prodname_copilot %} subscription, you will be automatically notified when you visit the {% data variables.product.prodname_copilot %} subscription page. If you do not meet the criteria for a free {% data variables.product.prodname_copilot %} subscription, you will be offered a 60 day free trial, after which a paid subscription is required for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+O {% data variables.product.prodname_copilot %} é um recurso pago, exigindo uma assinatura mensal ou anual. Os alunos, os professores e os mantenedores verificados de projetos populares de software livre do {% data variables.product.prodname_dotcom %} estão qualificados para usar o {% data variables.product.prodname_copilot %} gratuitamente. Se você atender aos critérios de uma assinatura gratuita do {% data variables.product.prodname_copilot %}, será notificado automaticamente quando visitar a página de assinatura do {% data variables.product.prodname_copilot %}. Se você não atender aos critérios de uma assinatura gratuita do {% data variables.product.prodname_copilot %}, será oferecida uma avaliação gratuita de 60 dias. Depois desse período será necessária uma assinatura paga para continuar o uso. Para obter mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)".
 
-## About the license for the {% data variables.product.prodname_copilot %} plugin in JetBrains IDEs
+## Sobre a licença do plug-in {% data variables.product.prodname_copilot %} nos IDEs da JetBrains
 
-{% data variables.product.prodname_dotcom %}, Inc. is the licensor of the JetBrains plugin. The end user license agreement for this plugin is the [{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) and use of this plugin is subject to those terms. JetBrains has no responsibility or liability in connection with the plugin or such agreement. By using the plugin, you agree to the foregoing terms.
+O {% data variables.product.prodname_dotcom %}, Inc. é o licenciante do plug-in da JetBrains. O uso desse plug-in está sujeito aos [Termos para produtos e recursos adicionais do {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot). A JetBrains não tem nenhuma responsabilidade relacionada ao plug-in nem a esse contrato. Usando o plug-in, você concorda com os termos anteriores.
 
-## Further reading
+## Leitura adicional
 
-- "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)"
+- "[Termos para produtos e recursos adicionais do {% data variables.product.company_short %}](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)"

translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md

@@ -80,7 +80,8 @@ Name | Description
 **`admin:enterprise`** | Gives full control of enterprise functionality. For more information, see "[Managing enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation.<br><br>Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`. 
 &emsp;`manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %}
 &emsp;`manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %}
-&emsp;`read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}
+&emsp;`read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}{% ifversion read-audit-scope %}
+**`read:audit_log`** | Read audit log data.{% endif %}
 {% note %}
 
 **Note:** Your OAuth App can request the scopes in the initial redirection. You

translations/pt-BR/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md

@@ -6,12 +6,12 @@ versions:
 topics:
   - Webhooks
 shortTitle: Receiving webhooks with the GitHub CLI
-ms.openlocfilehash: 2772a9d4208d0afe77871255ad6510b7f39de8d5
-ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.openlocfilehash: 11bc5b476a191a61594cb73f1e6ce1be5bb6cf9b
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 11/04/2022
-ms.locfileid: '148132960'
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160661'
 ---
 ## Sobre como receber webhooks com {% data variables.product.prodname_cli %}
 
@@ -29,7 +29,7 @@ Ao fazer alterações no código de integração, execute-o em um ambiente local
 
 {% endnote %}
 
-## Receber webhooks com o {% data variables.product.prodname_cli %}
+## Como receber webhooks com a {% data variables.product.prodname_cli %}
 
 {% data reusables.cli.cli-learn-more %}
 

translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md

@@ -20,6 +20,8 @@ As a discussions maintainer, you can create community resources to encourage dis
 
 When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
 
+You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
+
 For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
 
 {% data reusables.discussions.you-can-label-discussions %}
@@ -40,23 +42,63 @@ You can also move a discussion to a different category. It's not possible to mov
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
-  !["Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png)
+
+   ![Screenshot of the "Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png)
+
 1. Click a category.
-  !["Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png)
+
+   ![Screenshot of the "Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png)
 
 ## Pinning a discussion
 
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+{% ifversion discussions-category-specific-pins %}
+You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+
+This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+
+![Screenshot of a globally pinned discussion and a discussion pinned to the Ideas category](/assets/images/help/discussions/overview-pinned-discussions.png)
+
+### Pinning a discussion globally
+{% endif %}
+
+You can pin up to four important discussions above the list of discussions for the repository or organization. 
+
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
-  !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png)
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Pin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %}
+
+   ![Screenshot of the "Pin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png){% endif %}
+
 1. Optionally, customize the look of the pinned discussion.
-  ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
+   ![Screenshot of customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
 1. Click **Pin discussion**.
-  !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+   ![Screenshot of the "Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+{% ifversion discussions-category-specific-pins %}
+### Pinning a discussion to a category
+
+You can pin up to four important discussions above the list of discussions in a specific category. 
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+   
+   ![Screenshot of the "Pin discussion to CATEGORY" option in right sidebar for discussion](/assets/images/help/discussions/pin-discussion-to-category.png)
+
+2. To confirm, click **Pin to CATEGORY**.
+
+   ![Screenshot of the "Pin discussion to CATEGORY" modal](/assets/images/help/discussions/pin-discussion-to-category-modal.png)
+
+{% endif %}
 
 ## Editing a pinned discussion
 
@@ -66,21 +108,60 @@ Editing a pinned discussion will not change the discussion's category. For more
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
-  !["Edit pinned discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png)
+  {% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Edit pinned discussion" option in right sidebar for discussion](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png) {% else %}
+
+
+   ![Screenshot of the "Edit pinned discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png){% endif %}
+
 1. Customize the look of the pinned discussion.
-  ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
+  ![Screenshot of customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
 1. Click **Pin discussion**.
-  !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+  ![Screenshot of the "Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
 
 ## Unpinning a discussion
 
+{% ifversion discussions-category-specific-pins %}
+
+You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+
+### Unpinning a globally pinned discussion
+
+You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+{% endif %}
+
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
-  !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png)
+
+  ![Screenshot of the "Unpin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png)
+
 1. Read the warning, then click **Unpin discussion**.
-  !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png)
+
+  ![Screenshot of the "Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png)
+
+{% ifversion discussions-category-specific-pins %}
+### Unpinning a discussion from a category
+
+You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+
+   ![Screenshot of the "Unpin discussion from this category" option in right sidebar for discussion](/assets/images/help/discussions/unpin-discussion-from-category.png)
+
+1. Read the warning, then click **Unpin from this category**.
+
+   ![Screenshot of the "Unpin from this category" button in the "Unpin this discussion from this category" modal](/assets/images/help/discussions/unpin-discussion-from-category-modal.png)
+
+{% endif %}
 
 ## Transferring a discussion
 
@@ -89,12 +170,21 @@ To transfer a discussion, you must have permissions to create discussions in the
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**.
-  !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png)
+1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Transfer discussion" option in right sidebar for discussion](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %}
+
+  
+   ![Screenshot of the "Transfer discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png){% endif %}
+
 1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
-  !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
+
+   ![Screenshot of the "Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
+
 1. Click **Transfer discussion**.
-  !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png)
+
+   ![Screenshot of the "Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png)
 
 ## Deleting a discussion
 
@@ -102,9 +192,16 @@ To transfer a discussion, you must have permissions to create discussions in the
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
-  !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png)
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Delete discussion" option in right sidebar for discussion](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% else %}
+
+
+   ![Screenshot of the "Delete discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png){% endif %}
+
 1. Read the warning, then click **Delete this discussion**.
-  !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png)
+
+   ![Screenshot of the "Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png)
 
 ## Converting issues based on labels
 

translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md

@@ -1,41 +1,47 @@
 ---
-title: Moderar discussões
-intro: 'Você pode promover uma colaboração saudável marcando comentários como respostas, bloqueando ou desbloqueando discussões, convertendo problemas em discussões, editando ou excluindo comentários, discussões e categorias que não estão alinhados com{% ifversion fpt or ghec %} o código de conduta da comunidade{% elsif ghes > 3.5 %} as diretrizes de contribuição da organização{% endif %}.'
+title: Moderating discussions
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
   feature: discussions
-ms.openlocfilehash: 7d128c9beadb190f9c22c345cf0c3124b1dfcfcb
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147410112'
 ---
-## Sobre a moderação de discussões
 
-{% data reusables.discussions.about-discussions %} Se você tiver permissões de triagem para um repositório, você poderá ajudar a moderar as discussões desse repositório marcando comentários como respostas, bloqueando discussões que não são mais úteis ou que prejudicam a comunidade e convertendo os problemas em discussões quando uma ideia ainda está nos primeiros estágios de desenvolvimento. Da mesma forma, se você tiver permissão de triagem para o repositório de origem para discussões da organização, poderá moderar as discussões para essa organização.
 
-## Marcar um comentário como uma resposta
+## About moderating discussions
+
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
+
+## Marking a comment as an answer
 
 {% data reusables.discussions.marking-a-comment-as-an-answer %}
 
-## Bloquear discussões
+## Locking discussions
 
-É apropriado bloquear uma conversa quando toda a conversa não for construtiva ou violar o código de conduta da sua comunidade ou as [Diretrizes da Comunidade](/free-pro-team@latest/github/site-policy/github-community-guidelines) do {% data variables.product.prodname_dotcom %}. Você também pode bloquear uma conversa para evitar comentários em uma discussão que você deseja usar como um anúncio para a comunidade. Quando você bloqueia uma conversa, as pessoas com acesso de gravação ao repositório ou repositório de origem para discussões da organização ainda poderão comentar a discussão.
+It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion.
 
-{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %}
-1. Na lista de discussões, clique na discussão que você deseja bloquear.
-  ![Bloquear uma discussão](/assets/images/help/discussions/unanswered-discussion.png)
-1. Na margem direita de uma discussão, clique em **Bloquear conversa**.
-1. Leia as informações sobre como bloquear conversas e clique em **Bloquear conversa nesta discussão**.
-1. Quando estiver pronto para desbloquear a conversa, clique em **Desbloquear conversa** e clique em **Desbloquear conversa nesta discussão**.
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+1. In the list of discussions, click the discussion you want to lock.
+  ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png)
+1. In the right margin of a discussion, click **Lock conversation**.
+1. Read the information about locking conversations and click **Lock conversation on this discussion**.
+1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**.
 
-## Converter um problema em uma discussão
+## Converting an issue to a discussion
 
-Ao converter um problema em uma discussão, a discussão será criada automaticamente usando o conteúdo do problema. Pessoas com acesso de gravação a um repositório ou repositório de origem para discussões da organização podem converter problemas em massa com base em rótulos. Para obter mais informações, confira "[Gerenciar discussões](/discussions/managing-discussions-for-your-community/managing-discussions)".
+When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
 
-{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.repositories.sidebar-issues %}
-1. Na lista de problemas, clique no problema que deseja converter.
-1. Na margem direita de um problema, clique em **Converter em discussão**.
-1. Selecione o menu suspenso **Escolher uma categoria** e clique em uma categoria para ver a discussão.
-1. Clique em **Entendi. Converter este problema em uma discussão**.
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.repositories.sidebar-issues %}
+1. In the list of issues, click the issue you'd like to convert.
+1. In the right margin of an issue, click **Convert to discussion**.
+1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
+1. Click **I understand, convert this issue to a discussion**.
+
+{% ifversion discussions-hide-comments-on-block %}
+## Blocking a user from your organization
+
+Organization owners and moderators can block a user from the organization if their comments don't align with the community's code of conduct. When you block a user, they will no longer be able to comment on discussions. You can also hide all of the comments a user has made in the organization. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
+
+{% data reusables.organizations.blocking-a-user %} 
+{% endif %}

translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md

@@ -33,15 +33,16 @@ Once you are a verified {% data variables.product.prodname_global_campus %} stud
 - Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand.
 - Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)."
 
-A free subscription for {% data variables.product.prodname_copilot %} is available to verified students with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
-
-{% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
+{% data variables.product.prodname_global_campus %} students also receive the following {% data variables.product.prodname_dotcom %} benefits.
+- **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
+- **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
 
 {% note %}
 
 **Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
 
 {% endnote %}
+
 ## Further reading
 
 - "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)"

translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md

@@ -212,8 +212,8 @@ $ git remote rm destination
 # Remove remote
 $ git remote -v
 # Verify it's gone
-> origin  https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch)
-> origin  https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
 ```
 
 {% warning %}

translations/pt-BR/content/get-started/index.md

@@ -23,7 +23,7 @@ versions:
   ghec: '*'
 layout: product-landing
 introLinks:
-  quickstart: /github/getting-started-with-github/quickstart
+  quickstart: /get-started/quickstart
 featuredLinks:
   guides:
     - /github/getting-started-with-github/githubs-products

translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md

@@ -29,7 +29,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
    ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
    ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
 5. Optionally, add a description of your fork.
    ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
@@ -184,7 +184,7 @@ For more information about how to push changes in {% data variables.product.prod
 
 At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
 
-To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://www.github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
+To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
 
 {% data variables.product.product_name %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**.
 

translations/pt-BR/content/get-started/quickstart/github-glossary.md

@@ -1,6 +1,6 @@
 ---
-title: GitHub glossary
-intro: 'This glossary introduces common Git and {% data variables.product.prodname_dotcom %} terminology.'
+title: Glossário do GitHub
+intro: 'Este glossário apresenta a terminologia comum do Git e de {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /articles/github-glossary
   - /github/getting-started-with-github/github-glossary
@@ -10,6 +10,12 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
+ms.openlocfilehash: 3595b29a43cd7181bf5203f892b3bee84a237c29
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160837'
 ---
 {% for glossary in glossaries %}
   ### {{ glossary.term }}
@@ -19,8 +25,8 @@ versions:
 
 ---
 
-## Further reading
+## Leitura adicional
 
-- [The Official Git Glossary](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html)
-- [Git documentation](https://git-scm.com/doc)
-- [Git command list](https://git-scm.com/docs)
+- [O glossário oficial do Git](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html)
+- [Documentação do Git](https://git-scm.com/doc)
+- [Lista de comandos do Git](https://git-scm.com/docs)

translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md

@@ -1,6 +1,6 @@
 ---
-title: Attaching files
-intro: You can convey information by attaching a variety of file types to your issues and pull requests.
+title: Anexando arquivos
+intro: É possível transmitir informações anexando diversos tipos de arquivo a problemas e solicitações de pull.
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests
   - /articles/issue-attachments
@@ -14,48 +14,51 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
+ms.openlocfilehash: 28ce895a23c83f410d4755ad4036673e5c816155
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160749'
 ---
-
 {% data reusables.repositories.anyone-can-view-anonymized-url %}
 
-To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
+Para anexar um arquivo a uma conversa sobre um problema ou pull request, arraste-o e solte-o dentro da caixa de comentários. Como alternativa, você pode clicar na barra na parte inferior da caixa de comentários para navegar, selecionar e adicionar um arquivo do seu computador.
 
-![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png)
+![Selecionar anexos do computador](/assets/images/help/pull_requests/select-bar.png)
 
-When you attach a file, it is uploaded immediately to {% data variables.product.product_name %} and the text field is updated to show the anonymized URL for the file. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+Quando você anexa um arquivo, ele é carregado imediatamente no {% data variables.product.product_name %} e o campo de texto é atualizado para mostrar a URL anônima do arquivo. {% ifversion fpt or ghec %}Para obter mais informações sobre as URLs anônimas, confira "[Sobre as URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% tip %}
 
-**Tip:** In many browsers, you can copy-and-paste images directly into the box.
+**Dica:** em muitos navegadores, você pode copiar e colar as imagens diretamente na caixa.
 
 {% endtip %}
 
-The maximum file size is:
-- 10MB for images and gifs{% ifversion fpt or ghec %}
-- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
-- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif ghes %}
-- 100MB for videos{% endif %}
-- 25MB for all other files
+O tamanho máximo do arquivo é:
+- 10 MB para imagens e GIFs{% ifversion fpt or ghec %}
+- 10MB para vídeos enviados para um repositório pertencentes a um usuário ou organização em um plano grátis do GitHub
+- 100 MB para vídeos carregados em um repositório pertencente a um usuário ou a uma organização em um plano pago do GitHub{% elsif ghes %}
+- 100MB para vídeos{% endif %}
+- 25MB para todos os outros arquivos
 
-We support these files:
+Arquivos compatíveis:
 
-* PNG (*.png*)
-* GIF (*.gif*)
-* JPEG (*.jpg*)
-{%- ifversion svg-support %}
-* SVG (*.svg*)
-{%- endif %}
-* Log files (*.log*)
-* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
-* Text files (*.txt*)
-* PDFs (*.pdf*)
-* ZIP (*.zip*, *.gz*, *.tgz*){% ifversion fpt or ghec or ghes %}
-* Video (*.mp4*, *.mov*, *.webm*){% endif %}
+* PNG ( *.png*)
+* GIF ( *.gif*)
+* JPEG ( *.jpg*) {%- ifversion svg-support %}
+* SVG ( *.svg*) {%- endif %}
+* Arquivos de log ( *.log*)
+* Documentos do Microsoft Word ( *.docx*), do PowerPoint ( *.pptx*) e Excel ( *.xlsx*)
+* Arquivos de texto ( *.txt*)
+* PDFs ( *.pdf*)
+* ZIP ( *.zip*, *.gz*, *.tgz*){% ifversion fpt or ghec or ghes %}
+* Vídeo ( *.mp4*, *.mov*, *.webm*){% endif %}
 
 {% ifversion fpt or ghec or ghes %}{% note %}
 
-**Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility.
+**Observação:** a compatibilidade de codec de vídeo é específica do navegador, e é possível que um vídeo carregado em um navegador não possa ser visualizado em outro. No momento, recomendamos o uso do h.264 para maior compatibilidade.
 
 {% endnote %}{% endif %}
 
-![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
+![Anexos GIF animados](/assets/images/help/pull_requests/dragging_images.gif)

translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md

@@ -23,11 +23,11 @@ children:
   - /about-your-organizations-news-feed
   - /viewing-insights-for-your-organization
 shortTitle: Collaborate with groups
-ms.openlocfilehash: 84851a7282452c4a8d31c420a4f82991cf1b6bd3
-ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.openlocfilehash: dd6c9950c29328c2170f58045f3a0dfeafe03637
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147875556'
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163425'
 ---
 

translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md

@@ -144,7 +144,7 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can inter
 
 {% else %}
 
-You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.
+You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
 
 {% ifversion ghec %}
 

translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md

@@ -1,134 +1,135 @@
 ---
-title: About custom repository roles
-intro: You can more granularly control access to your organization's repositories with custom repository roles.
+title: Sobre as funções personalizadas do repositório
+intro: 'Você pode controlar o acesso aos repositórios da sua organização de forma mais granular, com funções de repositório personalizadas.'
 versions:
   feature: custom-repository-roles
 topics:
   - Organizations
   - Teams
 shortTitle: About custom roles
+ms.openlocfilehash: c4e7f791b9402b45160b31aab2653bf80150ddee
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160685'
 ---
-
 {% data reusables.organizations.custom-repo-roles-ghec-only %}
 
-## About custom repository roles
+## Sobre as funções personalizadas do repositório
 
-To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams.
+Para executar quaisquer ações em {% data variables.product.product_name %}, como criar um pull request em um repositório ou alterar as configurações de cobrança de uma organização, uma pessoa deve ter acesso suficiente à conta ou recurso relevante. Esse acesso é controlado por permissões. Uma permissão é a capacidade de executar uma ação específica. Por exemplo, a capacidade de excluir um problema é uma permissão. Uma função é um conjunto de permissões que você pode atribuir a pessoas ou equipes.
 
-Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Dentro de uma organização, você pode atribuir funções ao nível da organização, equipe e repositório. Para obter mais informações sobre os diferentes níveis de funções, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-You can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
+Você pode ter um controle mais granular sobre as permissões concedidas no nível do repositório criando até três funções de repositório personalizadas. {% data reusables.organizations.about-custom-repo-roles %} Para obter mais informações, confira "[Como gerenciar funções de repositório personalizadas para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
 
-After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
+Depois de criar um cargo personalizado, qualquer pessoa com acesso de administrador a um repositório pode atribuir a função a um indivíduo ou equipe. Para obter mais informações, confira "[Como gerenciar o acesso de uma pessoa a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" e "[Como gerenciar o acesso de uma equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
 
 {% ifversion custom-repo-role-api %}
 
-You can also use the REST API to create and manage custom repository roles. For more information, see "[Custom Repository Roles](/rest/orgs/custom-roles)."
+Você também pode usar a API REST para criar e gerenciar funções de repositório personalizadas. Para obter mais informações, confira "[Funções de repositório personalizadas](/rest/orgs/custom-roles)".
 
 {% else %}
 
-You can also use the REST API to list the custom repository roles available in your organization. For more information, see "[Custom Repository Roles API](/rest/orgs/custom-roles)."
+Você também pode usar a API REST para listar as funções de repositório personalizadas disponíveis em sua organização. Para obter mais informações, confira "[API de funções de repositório personalizadas](/rest/orgs/custom-roles)".
 
 {% endif %}
 
-## About the inherited role
+## Sobre a função herdada
 
-When you create a custom repository role, you start by choosing an inherited role from a set of pre-defined options. The inherited role determines the initial set of permissions included in the custom role. Then, you can further customize the role by choosing additional permissions to give the role. For the full list of available permissions, see "[Additional permissions for custom roles](#additional-permissions-for-custom-roles)."
+Ao criar uma função de repositório personalizado, você começa escolhendo uma função herdada de um conjunto de opções predefinidas. A função herdada determina o conjunto inicial de permissões incluídas na função personalizada. Em seguida, você pode personalizar ainda mais a função escolhendo as permissões adicionais para dar à função. Para ver a lista completa de permissões disponíveis, confira "[Permissões adicionais para funções personalizadas](#additional-permissions-for-custom-roles)".
 
-Your options for the inherited role are standardized for different types of contributors in your repository.
+As suas opções para a função herdada são padronizadas para diferentes tipos de contribuidores do seu repositório.
 
-| Inherited role | Designed for |
+| Função herdada | Criado para |
 |----|----|
-| **Read** | Non-code contributors who want to view or discuss your project |
-| **Triage** | Contributors who need to proactively manage issues and pull requests without write access |
-| **Write** | Organization members and collaborators who actively push to your project |
-| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions |
+| **Leitura** | Contribuidores sem código que querem ver ou discutir seu projeto |
+| **Triagem** | Os colaboradores que precisam gerenciar proativamente problemas e pull requests sem acesso de gravação |
+| **Gravar** | Integrantes e colaboradores da organização que fazem push ativamente no seu projeto |
+| **Manter** | Gerentes de projeto que precisam gerenciar o repositório sem acesso a ações sensíveis ou destrutivas |
 
-## Custom role examples
+## Exemplos de função personalizada
 
-Here are some examples of custom repository roles you can configure.
+Aqui estão alguns exemplos de funções de repositórios personalizados que você pode configurar.
 
-| Custom repository role | Summary | Inherited role | Additional permissions |
+| Função do repositório personalizado | Resumo | Função herdada | Permissões adicionais |
 |----|----|----|----|
-| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results |
-| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks |
-| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
+| Engenheiro de segurança | Capaz de contribuir com código e manter o pipeline de segurança | **Manter** | Excluir resultados da varredura de código |
+| Prestador de serviço | Capaz de desenvolver integrações de webhooks | **Gravar** | Gerenciar webhooks |
+| Gerente de comunidade | Capaz de lidar com todas as interações da comunidade sem ser capaz de contribuir com código | **Leitura** | – Marcar um problema como duplicado <br> – Gerenciar as configurações de página do GitHub <br> – Gerenciar as configurações do wiki <br> – Definir a visualização social <br> – Editar os metadados do repositório <br> – Discussões sobre triagem |
 
-## Additional permissions for custom roles
+## Permissões adicionais para funções personalizadas
 
-After choosing an inherited role, you can select additional permissions for your custom role.
+Depois de escolher uma função herdada, você poderá selecionar as permissões adicionais para a sua função personalizada.
 
-You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role.
+Você só pode escolher uma permissão adicional se já não estiver incluída na função herdada. Por exemplo, se a função herdada oferecer acesso de **Gravação** em um repositório, a permissão "Fechar uma solicitação de pull" já estará incluída na função herdada.
 
 {% ifversion discussions %}
-### Discussions
+### Discussões
 
-- Create a discussion category
-- Edit a discussion category
-- Delete a discussion category 
-- Mark or unmark discussion answers 
-- Hide or unhide discussion comments 
-- Convert issues to discussions 
+- Criar uma categoria de discussão
+- Editar uma categoria de discussão
+- Excluir uma categoria de discussão 
+- Marcar ou desmarcar respostas de discussão 
+- Ocultar ou mostrar comentários da discussão 
+- Converter problemas em discussões 
 
-For more information, see "[{% data variables.product.prodname_discussions %}](/discussions)."
+Para obter mais informações, confira "[{% data variables.product.prodname_discussions %}](/discussions)".
 {% endif %}
 
-### Issue and Pull Requests
+### Problemas e Pull Requests
 
-- Assign or remove a user 
-- Add or remove a label 
+- Atribuir ou remover um usuário 
+- Adicionar ou remover um rótulo 
 
-### Issue
+### Problema
 
-- Close an issue
-- Reopen a closed issue
-- Delete an issue
-- Mark an issue as a duplicate
+- Fechar um problema
+- Reabrir um problema fechado
+- Excluir um problema
+- Marcar um problema como duplicado
 
 ### Pull Request
 
-- Close a pull request
-- Reopen a closed pull request
-- Request a pull request review
+- Fechar uma solicitação de pull
+- Reabrir uma solicitação de pull fechada
+- Solicitar uma revisão de solicitação de pull
 
-### Repository
+### Repositório
 
-- Set milestones
-- Manage wiki settings 
-- Manage project settings
-- Manage pull request merging settings 
-- Manage {% data variables.product.prodname_pages %} settings (see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)")
-- Manage webhooks 
-- Manage deploy keys 
-- Edit repository metadata
-{%- ifversion ghec %}
-- Set interaction limits
-{%- endif %}
-- Set the social preview 
-- Push commits to protected branches (branch protection rules will still apply)
-- Create protected tags
-- Delete protected tags
-{%- ifversion bypass-branch-protections %}
-- Bypass branch protections
-{%- endif %}
+- Definir os marcos
+- Gerenciar as configurações do wiki 
+- Gerenciar as configurações do projeto
+- Gerenciar as configurações de mesclagem de solicitação de pull 
+- Gerenciar as configurações do {% data variables.product.prodname_pages %} (confira "[Como configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)")
+- Gerenciar webhooks 
+- Gerenciar as chaves de implantação 
+- Editar os metadados do repositório {%- ifversion ghec %}
+- Definir os limites de interação {%- endif %}
+- Definir a visualização social 
+- Efetuar push de commits para branches protegidos (as regras de proteção de branch ainda serão aplicadas)
+- Criar marcas protegidas
+- Excluir marcas protegidas {%- ifversion bypass-branch-protections %}
+- Ignorar as proteções de branch {%- endif %}
 
-### Security
+### Segurança
 
-- View {% data variables.product.prodname_code_scanning %} results 
-- Dismiss or reopen {% data variables.product.prodname_code_scanning %} results
-- Delete {% data variables.product.prodname_code_scanning %} results 
-- View {% data variables.product.prodname_dependabot_alerts %} 
-- Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %} 
-- View {% data variables.product.prodname_secret_scanning %} results 
-- Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results 
+- Exibir os resultados da {% data variables.product.prodname_code_scanning %} 
+- Ignorar ou reabrir os resultados da {% data variables.product.prodname_code_scanning %}
+- Excluir os resultados da {% data variables.product.prodname_code_scanning %} 
+- Exibir os {% data variables.product.prodname_dependabot_alerts %} 
+- Ignorar ou reabrir os {% data variables.product.prodname_dependabot_alerts %} 
+- Exibir os resultados da {% data variables.product.prodname_secret_scanning %} 
+- Ignorar ou reabrir os resultados da {% data variables.product.prodname_secret_scanning %} 
 
-## Precedence for different levels of access
+## Precedência para diferentes níveis de acesso
 
-If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role.
+Se uma pessoa receber diferentes níveis de acesso por meio de caminhos diferentes como, por exemplo, a associação a uma equipe e as permissões básicas para uma organização, o maior acesso substitui os outros. Por exemplo, se um proprietário da organização dá a um integrante da organização uma função personalizada que use a função de "ler" herdada e, em seguida, o proprietário da organização definir a permissão de base da organização para "gravar", essa função personalizada terá acesso de gravação, junto com quaisquer permissões adicionais incluídas na função personalizada.
 
 {% data reusables.organizations.mixed-roles-warning %}
 
-To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see:
-  - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
-  - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
-  - "[Editing a repository role](#editing-a-repository-role)"
+Para resolver o acesso conflitante, você pode ajustar as permissões básicas da sua organização ou o acesso da equipe ou editar a função personalizada. Para obter mais informações, consulte:
+  - "[Como definir as permissões base de uma organização](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
+  - "[Como gerenciar o acesso da equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
+  - "[Como editar uma função do repositório](#editing-a-repository-role)"

translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md

@@ -183,18 +183,18 @@ By default, you can only use npm packages hosted on your enterprise, and you wil
 {% data reusables.package_registry.authenticate-step %}
 {% data reusables.package_registry.create-npmrc-owner-step %}
 {% data reusables.package_registry.add-npmrc-to-repo-step %}
-4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency.
+1. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. Replace `<organization_name>/<package_name>` with your package dependency.
 
   ```json
   {
     "name": "@my-org/server",
     "version": "1.0.0",
-    "description": "Server app that uses the @octo-org/octo-app package",
+    "description": "Server app that uses the <organization_name>/<package_name> package",
     "main": "index.js",
     "author": "",
     "license": "MIT",
     "dependencies": {
-      "@octo-org/octo-app": "1.0.0"
+      "<organization_name>/<package_name>": "1.0.0"
     }
   }
   ```

translations/pt-BR/content/repositories/creating-and-managing-repositories/index.md

@@ -26,11 +26,11 @@ children:
   - /deleting-a-repository
   - /restoring-a-deleted-repository
 shortTitle: Create & manage repositories
-ms.openlocfilehash: ec9aa9879765356ab7a1ba0f74017f55b18425a6
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 06a0bfa43ca81b6b1feb2e796cacac051fb11749
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145127081'
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163551'
 ---
 

translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md

@@ -32,6 +32,7 @@ Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sit
 | PHP        | ✅                           |                         |
 | Python     | ✅                           | ✅                      |
 | Ruby       | ✅                           |                         |
+| Rust       | ✅                           |                         |
 | TypeScript | ✅                           |                         |
 
 

translations/pt-BR/content/rest/dependency-graph/dependency-review.md

@@ -1,6 +1,6 @@
 ---
-title: Dependency review
-intro: 'The Dependency review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment.'
+title: Análise de dependência
+intro: A API Revisão de dependência permite que você entenda as alterações de dependência e o impacto na segurança dessas alterações antes de adicioná-las ao ambiente.
 versions:
   fpt: '*'
   ghes: '>=3.6'
@@ -10,8 +10,13 @@ topics:
   - API
 miniTocMaxHeadingLevel: 3
 allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 9988c87ed4b0dcbe9c8a0694ebe0ca43d5bc336e
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164220'
 ---
+## Sobre a API de Revisão de Dependência
 
-## About the Dependency review API
-
-The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+A API de Revisão de Dependência permite que você entenda as alterações de dependência e o impacto na segurança dessas alterações antes de adicioná-las ao seu ambiente. Você pode ver a comparação de dependências entre dois commits de um repositório, incluindo dados de vulnerabilidade para todas as atualizações de versão com vulnerabilidades conhecidas. Para obter mais informações sobre a revisão de dependência, confira "[Sobre a revisão de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)".

translations/pt-BR/content/rest/overview/libraries.md

@@ -11,25 +11,25 @@ versions:
   ghec: '*'
 topics:
   - API
-ms.openlocfilehash: 4fa9e97ca9fa3803cfbd0cf0e21d3d2253a7aa60
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: aa139c0d25354260ccf688079f3e15a871b627bd
+ms.sourcegitcommit: 0ed77777360ec29eee7cd4fc212ae36fdd97c0bc
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146769154'
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148160959'
 ---
-<div class="jumbotron libraries-jumbotron">
-  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
-  <h1>O Octokit tem muitos sabores</h1>
-  <p class="lead">Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.</p>
-  <div class="octokit-links"><br/>
-     <div class="octokit-language"><span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
-     <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
-  </div>
-</div>
+![O Gundamcat](/assets/images/gundamcat.png)
 
-# Bibliotecas de terceiros
+## O Octokit tem muitos sabores
+
+Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.
+
+- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
+- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
+- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
+- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+
+## Bibliotecas de terceiros
 
 ### Clojure
 
@@ -130,6 +130,7 @@ ms.locfileid: '146769154'
 |**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)|
 |**github-flask**|[github-flask (site oficial)](http://github-flask.readthedocs.org)|
 |**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
+|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
 
 ### Ruby
 

translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md

@@ -1,10 +1,7 @@
----
-ms.openlocfilehash: 3def1c7efad50b8bfda097251abf28dd4a5f46df
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145083859"
----
-1. Em **Criar fork de fluxos de trabalho de solicitação de pull**, selecione suas opções. Por exemplo: ![Habilitar, desabilitar ou limitar ações para este repositório](/assets/images/help/settings/actions-fork-pull-request-workflows.png)
-1. Clique em **Salvar** para aplicar as configurações.
+1. Under **Fork pull request workflows**, select your options. For example:
+  {% ifversion actions-private-fork-workflow-approvals %}
+   ![Enable, disable, or limits actions for this repository](/assets/images/help/settings/actions-fork-pull-request-workflows-require-approval.png){% else %}
+
+   ![Enable, disable, or limits actions for this repository](/assets/images/help/settings/actions-fork-pull-request-workflows.png){% endif %}
+
+1. Click **Save** to apply the settings.

translations/pt-BR/data/reusables/actions/private-repository-forks-options.md

@@ -1,11 +1,4 @@
----
-ms.openlocfilehash: 6c1dd36680cbcbf04fda2d18f14a828249715ff7
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145065400"
----
-- **Executar fluxos de trabalho por meio de solicitações de pull com fork** – Permite que os usuários executem fluxos de trabalho por meio de solicitações de pull com fork usando um `GITHUB_TOKEN` com permissão somente leitura e sem acesso aos segredos.
-- **Enviar tokens de gravação para fluxos de trabalho por meio de solicitações de pull** – Permite que as solicitações de pull de forks usem um `GITHUB_TOKEN` com permissão de gravação.
-- **Enviar segredos para fluxos de trabalho por meio de solicitações de pull** – Disponibiliza todos os segredos para a solicitação de pull.
+- **Run workflows from fork pull requests** - Allows users to run workflows from fork pull requests, using a `GITHUB_TOKEN` with read-only permission, and with no access to secrets.
+- **Send write tokens to workflows from pull requests** - Allows pull requests from forks to use a `GITHUB_TOKEN` with write permission.
+- **Send secrets to workflows from pull requests** - Makes all secrets available to the pull request.{% ifversion actions-private-fork-workflow-approvals %}
+- **Require approval for fork pull request workflows** - Workflow runs on pull requests from collaborators without write permission will require approval from someone with write permission before they will run.{% endif %}

translations/pt-BR/data/reusables/actions/workflows/approve-workflow-runs.md

@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: fec57b88af5ef5b7227d88a8c70e5a4b4bb9c769
+ms.sourcegitcommit: fdc4466e89467a7b13239e26c6042dc1428946b6
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163808"
+---
+Os mantenedores com acesso de gravação a um repositório podem usar o seguinte procedimento para revisar e executar fluxos de trabalho em pull requests de colaboradores que exigem aprovação.
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
+1. Inspecione as alterações propostas no pull request e certifique-se de que você esteja confortável em executar seus fluxos de trabalho no branch do pull request. Você deve ficar especialmente atento para todas as alterações propostas no diretório `.github/workflows/` que afetem arquivos de fluxo de trabalho.
+1. Se você estiver familiarizado com a execução de fluxos de trabalho no branch de solicitação de pull, volte à guia {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversa** e, em "Fluxos de trabalho que aguardam aprovação", clique em **Aprovar e executar**.
+
+   ![Aprovar e executar fluxos de trabalho](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)

translations/pt-BR/data/reusables/code-scanning/autobuild-compiled-languages.md

@@ -1 +1,9 @@
-For the supported compiled languages, you can use the `autobuild` action in the {% data variables.code-scanning.codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
+---
+ms.openlocfilehash: 982b04961e4f780a5f1e284dad5620157f68569b
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161059"
+---
+Para as linguagens compiladas compatíveis, use a ação `autobuild` no {% data variables.code-scanning.codeql_workflow %} para compilar o código. Isso evita que você precise especificar comandos de build explícitos para C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} e Java.

translations/pt-BR/data/reusables/code-scanning/codeql-runner-analyze-example.md

@@ -1,4 +1,12 @@
-1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. The results will appear in the **Security** tab for your repository.
+---
+ms.openlocfilehash: e6d7a33506174bf50d70ae9b5d4ac9857cd880ae
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161225"
+---
+1. Preencha os bancos de dados do {% data variables.product.prodname_codeql %}, analise-os e carregue os resultados no {% data variables.product.product_name %}. Os resultados serão exibidos na guia **Segurança** do repositório.
 
     ```shell
     $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
@@ -9,7 +17,7 @@
     > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
     > Successfully uploaded results
     ```
-2. To upload {% data variables.product.prodname_code_scanning %} results as pull request checks, specify the pull request using the <nobr>`--ref`</nobr> flag. We recommend setting up the {% data variables.code-scanning.codeql_runner %} so that it runs on the [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request) webhook event.
+2. Para carregar os resultados da {% data variables.product.prodname_code_scanning %} como verificações de solicitação de pull, especifique a solicitação de pull usando o sinalizador <nobr>`--ref`</nobr>. Recomendamos configurar o {% data variables.code-scanning.codeql_runner %} para que ele seja executado no evento de webhook [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request).
 
     ```shell
     $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
@@ -21,4 +29,4 @@
     > Successfully uploaded results
     ```
 
-For more information about viewing {% data variables.product.prodname_code_scanning %} alerts, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)."
+Para obter mais informações sobre como ver alertas da {% data variables.product.prodname_code_scanning %}, confira "[Como fazer a triagem de alertas da verificação de código em solicitações de pull](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)" e "[Como gerenciar alertas da verificação de código para seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)".

translations/pt-BR/data/reusables/code-scanning/edit-workflow.md

@@ -1 +1,9 @@
-Typically, you don't need to edit the default workflow for {% data variables.product.prodname_code_scanning %}. However, if required, you can edit the workflow to customize some of the settings. For example, you can edit {% data variables.product.prodname_dotcom %}'s {% data variables.code-scanning.codeql_workflow %} to specify the frequency of scans, the languages or directories to scan, and what {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} looks for in your code. You might also need to edit the {% data variables.code-scanning.codeql_workflow %} if you use a specific set of commands to compile your code.
+---
+ms.openlocfilehash: a697342c2435c479a3309cfb4619c15d4521098e
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161220"
+---
+De modo geral, você não precisa editar o fluxo de trabalho padrão para {% data variables.product.prodname_code_scanning %}. No entanto, se necessário, você editar o fluxo de trabalho para personalizar algumas das configurações. Por exemplo, você pode editar o {% data variables.code-scanning.codeql_workflow %} do {% data variables.product.prodname_dotcom %} para especificar a frequência das verificações, as linguagens ou os diretórios a serem verificados e o que é procurado pela {% data variables.product.prodname_code_scanning %} do {% data variables.product.prodname_codeql %} no código. Talvez você precise editar o {% data variables.code-scanning.codeql_workflow %} caso use um conjunto específico de comandos para compilar o código.

translations/pt-BR/data/reusables/copilot/emus-cannot-use-copilot.md

@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 323e67dec23f2baa8b6e43779ed89e549d5ca198
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160754"
+---
+Os {% data variables.enterprise.prodname_managed_users_caps %} não podem usar o {% data variables.product.prodname_copilot %}.

translations/pt-BR/data/reusables/enterprise-accounts/emu-scim-note.md

@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 7527008260476000ac3460c800abd76b2fb202fe
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: b1c9d6341bb404267c34fa75e1a9c4c5eb401956
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145066027"
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160838"
 ---
 {% ifversion ghec%} {% note %}
 
-**Observação**: se a sua empresa usa o {% data variables.product.prodname_emus %}, você não pode usar a sincronização da equipe e, em vez disso, precisa configurar o SCIM para gerenciar a associação ao seu provedor de identidade. Para obter mais informações, confira "[Como configurar o provisionamento do SCIM para Usuários Gerenciados do Enterprise](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)".
+**Observação**: se a sua empresa usar o {% data variables.product.prodname_emus %}, você não precisará usar a sincronização de equipe. Em vez disso, você pode gerenciar a associação à equipe por meio da configuração do SCIM criada ao configurar sua empresa. Para obter mais informações, confira "[Como gerenciar associações à equipe com grupos de provedores de identidade](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)".
 
 {% endnote %} {% endif %}

translations/pt-BR/data/reusables/enterprise/ghec-authentication-options.md

@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1acdedabde1b516be6b8953861ed20cf6254ddb8
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163434"
+---
+Você pode optar por permitir que os membros criem e gerenciem contas de usuário ou a empresa pode criar e gerenciar as contas dos membros com {% data variables.product.prodname_emus %}. Se você permitir que os membros gerenciem suas próprias contas, também poderá configurar a autenticação SAML para aumentar a segurança e centralizar a identidade e o acesso para os aplicativos Web que sua equipe usa.

translations/pt-BR/data/reusables/gated-features/copilot.md

@@ -1,3 +1,11 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.copilot.emus-cannot-use-copilot %}<br><br>
+---
+ms.openlocfilehash: c408676063e80cca29eb7392181c00c4ecf7f76d
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160753"
+---
+{% data variables.product.prodname_copilot %} está disponível para clientes {% data variables.product.company_short %} com uma conta pessoal em {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.copilot.emus-cannot-use-copilot %}<br><br>
 
-{% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and maintainers of popular open source projects. If you are not a student, teacher, or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+O {% data variables.product.prodname_copilot %} é gratuito para uso de alunos, professores e mantenedores verificados de projetos populares de software livre. Se você não for aluno, professor nem mantenedor de um projeto popular de software livre, experimente o {% data variables.product.prodname_copilot %} gratuitamente com uma avaliação única de 60 dias. Após a avaliação gratuita, você precisará de uma assinatura paga para uso contínuo. Para ver mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)".

translations/pt-BR/data/reusables/github-connect/connection-port-protocol.md

@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3492d399c754d53fea2091a08c95b212455a8e18
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160752"
+---
+A conexão usa HTTPS nas portas 443 ou 80 e é protegida pelo TLS.

translations/pt-BR/data/reusables/gpg/paste-ssh-public-key.md

@@ -1,12 +1,11 @@
 ---
-ms.openlocfilehash: dc6bad5b656bb5d755196146b017213b66d1730e
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: 6dfaad4dc9dc813104183b2c9db41e480c9b27fb
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147884717"
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163574"
 ---
-1. Para definir sua chave de assinatura SSH no Git, cole o texto abaixo, substituindo o conteúdo da sua área de transferência pela chave que gostaria de usar. Como a chave contém espaços, você deve colocá-la entre aspas:
+1. Para definir a chave de assinatura SSH no Git, cole o texto abaixo, substituindo **/PATH/TO/KEY.PUB** pela chave pública que deseja usar.
   ```bash
-  $ git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com'
-  ```
+  $ git config --global user.signingkey /PATH/TO/.SSH/KEY.PUB

translations/pt-BR/data/reusables/organizations/blocking-a-user.md

@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 44fb7593fc71c38604cb0e7b96ea0439c7028a1f
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148164219"
+---
+Ao bloquear um usuário, você pode optar por bloqueá-lo indefinidamente ou por um período específico. Se você bloquear alguém por um período específico, ele será automaticamente desbloqueado após o término desse período. Se você bloquear alguém indefinidamente, será possível desbloqueá-lo manualmente a qualquer momento. Para obter mais informações, consulte "[Como bloquear um usuário da sua organização](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)".

translations/pt-BR/data/reusables/repositories/about-READMEs.md

@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a4b1ca4e0548ebc2be12a34e0bb1687e9e650038
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163421"
+---
+É possível adicionar um arquivo README a um repositório para comunicar informações importantes sobre o seu projeto. Um LEIAME, junto com uma licença de repositório, um arquivo de citação{% ifversion fpt or ghec %}, diretrizes de contribuição e um código de conduta{% elsif ghes %} e diretrizes de contribuição{% endif %}, comunica as expectativas do projeto e ajuda você a gerenciar contribuições.

translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md

@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 85c7f83e66e8519c6d62346fe69b6e3f0b413ff1
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 478008cfe79ec4fe3c32c154af38692879f5c807
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147419886"
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160750"
 ---
 {% warning %}
 
-**Aviso:** se você anexar um arquivo a uma solicitação de pull, a um comentário de problema, a um tíquete no {% data variables.contact.support_portal %}, qualquer pessoa poderá exibir a URL anônima sem autenticação, mesmo que a solicitação de pull esteja em um repositório privado{% ifversion ghes %} ou um modo privado esteja habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para obter mais informações sobre as URLs anônimas, confira "[Sobre as URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+**Aviso:** quando você carregar uma imagem ou um vídeo em uma solicitação de pull ou em um comentário de problema ou carregar um arquivo no {% data variables.contact.support_portal %}, qualquer pessoa poderá visualizar a URL anônima sem autenticação, mesmo que a solicitação de pull ou o problema esteja em um repositório privado{% ifversion ghes %} ou que o modo privado esteja habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para obter mais informações sobre as URLs anônimas, confira "[Sobre as URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}

translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md

@@ -1,31 +1,20 @@
 ---
-title: 批准复刻中的工作流程运行
-intro: 当外部贡献者第一次向公共仓库提交拉取请求时，拥有写入权限的维护者可能必须批准任何工作流程运行。
+title: Approving workflow runs from public forks
+intro: 'When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve any workflow runs.'
 versions:
   fpt: '*'
   ghec: '*'
 shortTitle: Approve public fork runs
-ms.openlocfilehash: b995362f67d97a3e2ee6d1029cbe24227867f58a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145084656'
 ---
-## 关于公共复刻中的工作流程运行
+
+## About workflow runs from public forks
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-可以为[存储库](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)、[组织](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks)或[企业](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)配置工作流审批要求。
+You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
 
-已等待批准超过 30 天的工作流程运行将自动删除。
+Workflow runs that have been awaiting approval for more than 30 days are automatically deleted.
 
-## 批准公共复刻中拉取请求的工作流程运行
+## Approving workflow runs on a pull request from a public fork
 
-能够写入仓库的维护者可按照以下步骤来审查和运行来自贡献者、需要审批的拉取请求上的工作流程。
-
-{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
-1. 检查拉取请求中的拟议更改，确保您在拉取请求分支上自由运行您的工作流程。 应特别注意 `.github/workflows/` 目录中影响工作流文件的任何拟议更改。
-1. 如果能自由在拉取请求分支上运行工作流，请返回到 {% octicon "comment-discussion" aria-label="The discussion icon" %}“转换”选项卡，在“等待审批的工作流”下，单击“批准并运行” 。
-
-   ![批准并运行工作流程](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
+{% data reusables.actions.workflows.approve-workflow-runs %}

translations/zh-CN/content/actions/managing-workflow-runs/index.md

@@ -1,6 +1,6 @@
 ---
 title: 管理工作流程运行
-shortTitle: Managing workflow runs
+shortTitle: Manage workflow runs
 intro: '可以重新运行或取消工作流程、{% ifversion fpt or ghes or ghae %}审核部署、{% endif %}查看可计费作业执行分钟数和下载项目。'
 redirect_from:
   - /actions/configuring-and-managing-workflows/managing-a-workflow-run
@@ -18,17 +18,18 @@ children:
   - /re-running-workflows-and-jobs
   - /canceling-a-workflow
   - /approving-workflow-runs-from-public-forks
+  - /approving-workflow-runs-from-private-forks
   - /reviewing-deployments
   - /disabling-and-enabling-a-workflow
   - /skipping-workflow-runs
   - /deleting-a-workflow-run
   - /downloading-workflow-artifacts
   - /removing-workflow-artifacts
-ms.openlocfilehash: fe5f7c461fc03392bcc93713887b1cc1d4293207
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 9e7d6f9c29fdfb2a387b84373c1140dbb3ef6713
+ms.sourcegitcommit: 73b91dd4cdf592eadec4252319379d6fbe92858e
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099188'
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164088'
 ---
 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}

translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md

@@ -49,19 +49,24 @@ For more information on workflow run artifacts, see "[Persisting workflow data u
 
 ## Restrictions for accessing a cache
 
-A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
+Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. 
+Workflow runs can restore caches created in either the current branch or the default branch (usually `main`). If a workflow run is triggered for a pull request, it can also restore caches created in the base branch, including base branches of forked repositories. For example, if the branch `feature-b` has the base branch `feature-a`, a workflow run triggered on a pull request would have access to caches created in the default `main` branch, the base `feature-a` branch, and the current `feature-b` branch.
 
-Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). On similar lines, a cache created for the tag `release-a` (from the base `main`) would not be accessible to a workflow triggered for the tag `release-b` (with the base `main`).
+Workflow runs cannot restore caches created for child branches or sibling branches. For example, a cache created for the child `feature-b` branch would not be accessible to a workflow run triggered on the parent `main` branch. Similarly, a cache created for the `feature-a` branch with the base `main` would not be accessible to its sibling `feature-c` branch with the base `main`. Workflow runs also cannot restore caches created for different tag names. For example, a cache created for the tag `release-a` with the base `main` would not be accessible to a workflow run triggered for the tag `release-b` with the base `main`.
 
-Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
+When a cache is created by a workflow run triggered on a pull request, the cache is created for the merge ref (`refs/pull/.../merge`). Because of this, the cache will have a limited scope and can only be restored by re-runs of the pull request. It cannot be restored by the base branch or other pull requests targeting that base branch.
+
+Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch.
 
 ## Using the `cache` action
 
-The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
+The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache that _exactly_ matches the key, the action restores the cached files to the `path` you configure.
+You can optionally provide a list of `restore-keys` to use in case the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can _partially_ match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
 
-If there is no exact match, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`.
+If there is an exact match to the provided `key`, this is considered a cache hit. If no cache exactly matches the provided `key`, this is considered a cache miss. On a cache miss, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. For more information about how this is handled, see "[Cache hits and misses](#cache-hits-and-misses)."
+
+You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key.
 
-You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
 
 ### Input parameters for the `cache` action
 
@@ -94,6 +99,21 @@ You can optionally provide a list of `restore-keys` to use when the `key` doesn'
 
 - `cache-hit`: A boolean value to indicate an exact match was found for the key.
 
+### Cache hits and misses
+When `key` exactly matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
+
+When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
+
+When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
+
+1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
+   - When there is an exact match, the action restores the files in the cache to the `path` directory.
+   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
+1. The `cache` action completes and the next step in the job runs.
+1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
+
+For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)."
+
 ### Example using the `cache` action
 
 This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
@@ -136,20 +156,6 @@ jobs:
         run: npm test
 ```
 
-When `key` matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
-
-When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
-
-When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
-
-1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
-   - When there is an exact match, the action restores the files in the cache to the `path` directory.
-   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
-1. The `cache` action completes and the next step in the job runs.
-1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
-
-For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)." Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
-
 ### Using contexts to create cache keys
 
 A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Expressions](/actions/learn-github-actions/expressions)."
@@ -185,7 +191,9 @@ In the example workflow above, there is a step that lists the state of the Node
 
 ## Matching a cache key
 
-The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
+The `cache` action first searches for cache hits for `key` and the cache _version_ in the branch containing the workflow run. If there is no hit, it searches for `restore-keys` and the _version_. If there are still no hits in the current branch, the `cache` action retries same steps on the default branch. Please note that the scope restrictions apply during the search. For more information, see "[Restrictions for accessing a cache](#restrictions-for-accessing-a-cache)."
+
+Cache version is a way to stamp a cache with metadata of the `path` and the compression tool used while creating the cache. This ensures that the consuming workflow run uniquely matches a cache it can actually decompress and use. For more information, see [Cache Version](https://github.com/actions/cache#cache-version) in the Actions Cache documentation.
 
 `restore-keys` allows you to specify a list of alternate restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches the `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
 

translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md

@@ -1,6 +1,6 @@
 ---
-title: About GitHub Connect
-intro: '{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by giving you access to additional features and workflows that rely on the power of {% data variables.product.prodname_dotcom_the_website %}.'
+title: 关于 GitHub Connect
+intro: '{% data variables.product.prodname_github_connect %} 通过允许你访问依赖于 {% data variables.product.prodname_dotcom_the_website %} 的力量的其他功能和工作流来增强 {% data variables.product.product_name %}。'
 versions:
   ghes: '*'
   ghae: '*'
@@ -9,76 +9,66 @@ topics:
   - Enterprise
   - GitHub Connect
 miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: ac4ec1d8b619e56c38013f5ae38d5782b6faec88
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160814'
 ---
+## 关于 {% data variables.product.prodname_github_connect %}
 
-## About {% data variables.product.prodname_github_connect %}
+{% data variables.product.prodname_github_connect %} 通过允许 {% data variables.location.product_location %} 以有限的方式从 {% data variables.product.prodname_dotcom_the_website %} 的强大功能中获益，从而增强了 {% data variables.product.product_name %}。 启用 {% data variables.product.prodname_github_connect %} 后，可以启用依赖于 {% data variables.product.prodname_dotcom_the_website %} 的其他功能和工作流，例如 {% data variables.product.prodname_advisory_database %} 中跟踪的安全漏洞的 {% data variables.product.prodname_dependabot_alerts %}。
 
-{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.location.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. 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 {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}.
+{% data variables.product.prodname_github_connect %} 不会将 {% data variables.location.product_location %} 打开到公共 Internet。 企业的任何私有数据都不会公开给 {% data variables.product.prodname_dotcom_the_website %} 用户。 相反，{% data variables.product.prodname_github_connect %} 仅传输你选择启用的各个功能所需的有限数据。 除非启用许可证同步，否则 {% data variables.product.prodname_github_connect %} 不会传输任何个人数据。 有关 {% data variables.product.prodname_github_connect %} 传输哪些数据的详细信息，请参阅“[{% data variables.product.prodname_github_connect %} 的数据传输](#data-transmission-for-github-connect)”。
 
-{% data variables.product.prodname_github_connect %} does not open {% data variables.location.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)."
+启用 {% data variables.product.prodname_github_connect %} 将不允许 {% data variables.product.prodname_dotcom_the_website %} 用户对 {% data variables.product.product_name %} 进行更改。
 
-Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}.
+若要启用 {% data variables.product.prodname_github_connect %}，需在 {% data variables.location.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %} 上使用 {% data variables.product.prodname_ghe_cloud %} 的组织或企业帐户之间配置连接。 {% data reusables.github-connect.connection-port-protocol %}有关详细信息，请参阅“[管理 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)”。
 
-To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+启用 {% data variables.product.prodname_github_connect %} 后，你将能够启用{% ifversion ghes %}用户许可证自动同步和 {% endif %}{% data variables.product.prodname_dependabot_alerts %} 等功能。 有关所有可用功能的详细信息，请参阅“[{% data variables.product.prodname_github_connect %} 功能](#github-connect-features)”。
 
-After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)."
+## {% data variables.product.prodname_github_connect %} 功能
 
-## {% data variables.product.prodname_github_connect %} features
+配置 {% data variables.location.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的连接后，便可为企业启用 {% data variables.product.prodname_github_connect %} 的各个功能。
 
-After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise.
+功能 | 说明 | 详细信息 | ------- | ----------- | ---------------- |{% ifversion ghes %} 用户许可证自动同步 | 通过自动将用户许可证从 {% data variables.location.product_location %} 同步到 {% data variables.product.prodname_ghe_cloud %} 来管理 {% data variables.product.prodname_enterprise %} 部署中的许可证使用情况。 |“[为企业启用用户许可证自动同步](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)”{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | 允许用户查找和修复代码依赖项中的漏洞。 |“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”{% endif %} {% data variables.product.prodname_dotcom_the_website %} 操作 | 允许用户在工作流文件中使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。 |“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)”{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | 从 GitHub Enterprise Server 分析自己的聚合数据，并帮助我们改进 GitHub 产品。 | [为企业启用 {% data variables.product.prodname_server_statistics %}](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise){% endif %} 统一搜索 | 从 {% data variables.location.product_location %} 搜索时，允许用户在搜索结果中包含 {% data variables.product.prodname_dotcom_the_website %} 上的存储库。 | [为企业启用 {% data variables.enterprise.prodname_unified_search %}](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)统一参与 | 允许用户将他们在 {% data variables.location.product_location %} 上的工作的匿名参与计数包含在 {% data variables.product.prodname_dotcom_the_website %} 上的参与图中。 | [为企业启用 {% data variables.enterprise.prodname_unified_contributions %}](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)
 
-Feature | Description | More information |
-------- | ----------- | ---------------- |{% ifversion ghes %}
-Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% 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 %}
-{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %}
-{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %}
-{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %}
-Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"
-Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.enterprise.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"
+## {% data variables.product.prodname_github_connect %} 的数据传输 
 
-## Data transmission for {% data variables.product.prodname_github_connect %} 
-
-When {% data variables.product.prodname_github_connect %} is enabled, a record on {% data variables.product.prodname_ghe_cloud %} stores information about the connection. If you enable individual features of {% data variables.product.prodname_github_connect %}, additional data is transmitted.
+启用 {% data variables.product.prodname_github_connect %} 时，{% data variables.product.prodname_ghe_cloud %} 上的记录会存储有关连接的信息。 如果启用 {% data variables.product.prodname_github_connect %} 的各个功能，则会传输其他数据。
 
 {% note %}
 
-**Note:** No repositories, issues, or pull requests are ever transmitted from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} by {% data variables.product.prodname_github_connect %}.
+注意：{% data variables.product.prodname_github_connect %} 从未将存储库、问题或拉取请求从 {% data variables.product.product_name %} 传输到 {% data variables.product.prodname_dotcom_the_website %}。
 
 {% endnote %}
 
-### Data transmitted when {% data variables.product.prodname_github_connect %} is enabled
+### 启用 {% data variables.product.prodname_github_connect %} 时传输的数据
 
-When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection.
+当你启用 {% data variables.product.prodname_github_connect %} 或特定的 {% data variables.product.prodname_github_connect %} 功能时，{% data variables.product.prodname_ghe_cloud %} 上的记录将存储有关连接的以下信息。
 {% ifversion ghes %}
-- The public key portion of your {% data variables.product.prodname_ghe_server %} license
-- A hash of your {% data variables.product.prodname_ghe_server %} license
-- The customer name on your {% data variables.product.prodname_ghe_server %} license
-- The version of {% data variables.location.product_location_enterprise %}{% endif %}
-- The hostname of {% data variables.location.product_location %}
-- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.location.product_location %}
-- The authentication token that's used by {% data variables.location.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %}
-- If Transport Layer Security (TLS) is enabled and configured on {% data variables.location.product_location %}{% ifversion ghes %}
-- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.location.product_location %}, and the date and time of enablement{% endif %}
-- The dormancy threshold for your enterprise
-- The number of dormant users for your enterprise
-- A count of license-consuming seats, which does not include suspended users
+- {% data variables.product.prodname_ghe_server %} 许可的公钥部分
+- {% data variables.product.prodname_ghe_server %} 许可的哈希
+- {% data variables.product.prodname_ghe_server %} 许可上的客户名称
+- {% data variables.location.product_location_enterprise %}{% endif %} 的版本
+- {% data variables.location.product_location %} 的主机名
+- {% data variables.product.prodname_ghe_cloud %} 上连接到 {% data variables.location.product_location %} 的组织或企业帐户
+- {% data variables.location.product_location %} 用于向 {% data variables.product.prodname_ghe_cloud %} 发出请求的身份验证令牌
+- 是否在 {% data variables.location.product_location %}{% ifversion ghes %} 上启用并配置了传输层安全性 (TLS)
+- 在 {% data variables.location.product_location %} 上启用的 {% data variables.product.prodname_github_connect %} 功能，以及启用日期和时间{% endif %}
+- 企业休眠阈值
+- 企业休眠用户数
+- 许可证消耗的席位计数，其中不包括暂停的用户
 
-{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled.
+{% data variables.product.prodname_github_connect %} 从启用 {% data variables.product.prodname_github_connect %} 的日期和大致时间开始每周同步 {% data variables.location.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的上述连接数据。
 
-### Data transmitted by individual features of {% data variables.product.prodname_github_connect %}
+### {% data variables.product.prodname_github_connect %} 的各个功能传输的数据
 
-Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}.
+如果启用 {% data variables.product.prodname_github_connect %} 的各个功能，则会传输其他数据。
 
-Feature | Data | Which way does the data flow? | Where is the data used? | 
-------- | ---- | --------- | ------ |{% ifversion ghes %}
-Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %}
-{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %}
-{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository<br><br>If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %}
-{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %}
-{% data variables.product.prodname_server_statistics %} | Aggregate metrics about your usage of {% data variables.product.prodname_ghe_server %}. For the complete list of metrics, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %}
-Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} |
-Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} |
+功能 | 数据 | 数据流向何方？ | 在哪里使用了数据？ | ------- | ---- | --------- | ------ |{% ifversion ghes %} 用户许可证自动同步 | 每个 {% data variables.product.product_name %} 用户的用户 ID 和电子邮件地址 | 从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | 漏洞警报 | 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | 依赖项和每个依赖项存储库的元数据<br><br>如果依赖项存储在 {% data variables.product.prodname_dotcom_the_website %} 上的专用存储库中，则只有在 {% data variables.product.prodname_dependabot %} 配置并授权访问该存储库时才会传输数据。 | 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} {% data variables.product.prodname_dotcom_the_website %} 操作 | 操作名称、操作（来自 {% data variables.product.prodname_marketplace %} 的 YAML 文件）| 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %}<br><br>从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | 聚合有关 {% data variables.product.prodname_ghe_server %} 使用情况的指标。 有关指标的完整列表，请参阅“[关于 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)”。 | 从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} 统一搜索 | 搜索词、搜索结果 | 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %}<br><br>从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | 统一参与 | 参与计数 | 从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} |
 
-## Further reading
+## 延伸阅读
 
-- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation
+- GraphQL API 文档中的“[企业帐户](/graphql/guides/managing-enterprise-accounts)”

translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md

@@ -1,7 +1,7 @@
 ---
-title: Managing GitHub Connect
+title: 管理 GitHub Connect
 shortTitle: Manage GitHub Connect
-intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.location.product_location %}.'
+intro: '可启用 {% data variables.product.prodname_github_connect %} 来访问 {% data variables.location.product_location %} 的其他功能和工作流。'
 redirect_from:
   - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com
   - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
@@ -20,71 +20,65 @@ topics:
   - GitHub Connect
   - Infrastructure
   - Networking
+ms.openlocfilehash: 30a170543b63c390aa8975b1ca57c265bc7fa8fa
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160646'
 ---
-
 {% data reusables.github-connect.beta %}
 
-## About {% data variables.product.prodname_github_connect %}
+## 关于 {% data variables.product.prodname_github_connect %}
 
-You can access additional features and workflows on {% data variables.location.product_location %} by enabling {% data variables.product.prodname_github_connect %}. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
+可以通过启用 {% data variables.product.prodname_github_connect %} 来访问 {% data variables.location.product_location %} 上的其他功能和工作流。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)”。
 
-When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %}
+启用 {% data variables.product.prodname_github_connect %} 时，需要在 {% data variables.location.product_location %} 与 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业帐户之间配置连接。 {% data reusables.github-connect.connection-port-protocol %}
 
-Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}.
+启用 {% data variables.product.prodname_github_connect %} 可以在 {% data variables.product.prodname_ghe_cloud %} 上创建组织或企业帐户所拥有的 {% data variables.product.prodname_github_app %}。 {% data variables.product.product_name %} 使用 {% data variables.product.prodname_github_app %} 的凭据向 {% data variables.product.prodname_ghe_cloud %} 发出请求。
 
-{% ifversion ghes %}
-{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}.
-- An authentication token, which is valid for one hour
-- A private key, which is used to generate a new authentication token
+{% ifversion ghes %} {% data variables.product.prodname_ghe_server %} 会存储来自 {% data variables.product.prodname_github_app %} 的凭据。 这些凭据将复制到任何高可用性或集群环境中的所有节点，并存储在任何备份中，包括由 {% data variables.product.prodname_enterprise_backup_utilities %} 创建的快照。
+- 有效期为一小时的身份验证令牌
+- 用于生成新的身份验证令牌的私钥 {% endif %}
+
+## 先决条件
+
+若要使用 {% data variables.product.prodname_github_connect %}，必须在使用 {% data variables.product.prodname_ghe_cloud %} 的 {% data variables.product.prodname_dotcom_the_website %} 上拥有组织或企业帐户。 你可能已将 {% data variables.product.prodname_ghe_cloud %} 包含在计划中。 {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% ifversion ghes %}如果 {% data variables.product.prodname_dotcom_the_website %} 上的组织或企业帐户使用 IP 允许列表，则必须将 {% data variables.location.product_location %} 的 IP 地址或网络添加到 {% data variables.product.prodname_dotcom_the_website %} 上的 IP 允许列表。 有关详细信息，请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[管理组织的允许 IP 地址](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)”或“[为企业中的安全设置实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)”。
+
+若要配置连接，代理配置必须允许连接到 `github.com`、`api.github.com` 和 `uploads.github.com`。 有关详细信息，请参阅“[配置出站代理服务器](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)”。
 {% endif %}
 
-## Prerequisites
+## 启用 {% data variables.product.prodname_github_connect %}
 
-To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %}
+如果企业所有者同时也是使用 {% data variables.product.prodname_ghe_cloud %} 的组织或企业帐户的所有者，可以启用 {% data variables.product.prodname_github_connect %}。
+
+如果要将 {% data variables.location.product_location %} 连接到 {% data variables.product.prodname_ghe_cloud %} 上不属于企业帐户的组织，则必须以组织所有者身份登录到 {% data variables.product.prodname_dotcom_the_website %}。
+
+如果要将 {% data variables.location.product_location %} 连接到 {% data variables.product.prodname_ghe_cloud %} 上企业帐户拥有的组织或者连接到企业帐户本身，则必须以企业所有者身份登录到 {% data variables.product.prodname_dotcom_the_website %}。
 
 {% ifversion ghes %}
-If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.location.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
-
-To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)."
-{% endif %}
-
-## Enabling {% data variables.product.prodname_github_connect %}
-
-Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}.
-
-If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner.
-
-If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner.
-
-{% ifversion ghes %}
-1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
-1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+1. 登录到 {% data variables.location.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. 登录到 {% data variables.location.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。
 {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
-1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features</a>."
-{% ifversion ghes %}
-  ![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %}
-  ![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png)
-{% endif %}
-1. Next to the enterprise account or organization you'd like to connect, click **Connect**.
-  ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
+1. 在“{% data variables.product.prodname_github_connect %} 尚未启用”下，单击“启用 {% data variables.product.prodname_github_connect %}”。 单击“启用 {% data variables.product.prodname_github_connect %}”，表示你同意“<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} 其他产品和功能的条款</a>”。
+{% ifversion ghes %} ![“启用 GitHub 连接”按钮](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} ![“启用 GitHub 连接”按钮](/assets/images/enterprise/github-ae/enable-github-connect-button.png) {% endif %}
+1. 在要连接的企业帐户或组织旁，单击“连接”。
+  ![企业帐户或企业旁边的“连接”按钮](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
 
-## Disabling {% data variables.product.prodname_github_connect %}
+## 禁用 {% data variables.product.prodname_github_connect %}
 
-Enterprise owners can disable {% data variables.product.prodname_github_connect %}.
+企业所有者可以禁用 {% data variables.product.prodname_github_connect %}。
 
-When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.location.product_location %} are deleted.
+与 {% data variables.product.prodname_ghe_cloud %} 断开连接后，{% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} 会从企业帐户或组织中删除，{% data variables.location.product_location %} 上存储的凭据也会删除。
 
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**.
-{% ifversion ghes %}
-  ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
-1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
-  ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)  
-{% else %}
-  ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/github-ae/disable-github-connect-button.png)
-1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
-  ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png)
-{% endif %} 
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+1. 在要断开连接的企业帐户或组织旁，单击“禁用 {% data variables.product.prodname_github_connect %}”。
+{% ifversion ghes %} ![企业帐户或组织名称旁的“禁用 GitHub Connect”按钮](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
+1. 阅读有关断开连接的信息，并单击“禁用 {% data variables.product.prodname_github_connect %}”。
+  ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)  
+{% else %} ![企业帐户或组织名称旁的“禁用 GitHub Connect”按钮](/assets/images/enterprise/github-ae/disable-github-connect-button.png)
+1. 阅读有关断开连接的信息，并单击“禁用 {% data variables.product.prodname_github_connect %}”。
+  ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) {% endif %} 

translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md

@@ -1,5 +1,5 @@
 ---
-title: Network ports
+title: 网络端口
 redirect_from:
   - /enterprise/admin/articles/configuring-firewalls
   - /enterprise/admin/articles/firewall
@@ -8,7 +8,7 @@ redirect_from:
   - /enterprise/admin/installation/network-ports
   - /enterprise/admin/configuration/network-ports
   - /admin/configuration/network-ports
-intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
+intro: 根据您需要为管理员、最终用户和电子邮件支持显示的网络服务有选择地打开网络端口。
 versions:
   ghes: '*'
 type: reference
@@ -17,56 +17,62 @@ topics:
   - Infrastructure
   - Networking
   - Security
+ms.openlocfilehash: 048b27ed44cea11057c781ae3043078a825f8d1a
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160652'
 ---
-## Administrative ports
+## 管理端口
 
-Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
+配置 {% data variables.location.product_location %} 并运行某些功能需要一些管理端口。 最终用户在使用基本应用程序时不需要管理端口。
 
-| Port | Service | Description |
+| 端口 | 服务 | 说明 |
 |---|---|---|
-| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
-| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. |
-| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
-| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
-| 123/UDP| NTP | Required for time protocol operation. |
-| 161/UDP | SNMP | Required for network monitoring protocol operation. |
+| 8443 | HTTPS | 基于安全 Web 的 {% data variables.enterprise.management_console %}。 进行基本安装和配置时需要。 |
+| 8080 | HTTP | 基于纯文本 Web 的 {% data variables.enterprise.management_console %}。 除非手动禁用 TLS，否则不需要。 |
+| 122 | SSH | {% data variables.location.product_location %} 的 shell 访问权限。 需要对高可用性配置中所有节点之间的传入连接开放。 默认 SSH 端口 (22) 专用于 Git 和 SSH 应用程序网络流量。 |
+| 1194/UDP | VPN | 采用高可用性配置的安全复制网络隧道。 需要对配置中所有节点之间的通信开放。|
+| 123/UDP| NTP | 为时间协议操作所需。 |
+| 161/UDP | SNMP | 为网络监视协议操作所需。 |
 
-## Application ports for end users
+## 最终用户的应用程序端口
 
-Application ports provide web application and Git access for end users.
+应用程序端口为最终用户提供 Web 应用程序和 Git 访问。
 
-| Port | Service | Description |
+| 端口 | 服务 | 说明 |
 |---|---|---|
-| 443 | HTTPS | Access to the web application and Git over HTTPS. |
-| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. |
-| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
-| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
+| 443 | HTTPS | 通过 HTTPS 访问 Web 应用程序和 Git。 |
+| 80 | HTTP | 访问 Web 应用程序。 如果配置了 TLS，则所有请求都将重定向到 HTTPS 端口。 |
+| 22 | SSH | 通过 SSH 访问 Git。 支持对公共和私有仓库执行克隆、提取和推送操作。 |
+| 9418 | Git | Git 协议端口支持通过未加密网络通信对公共仓库执行克隆和提取操作。 {% data reusables.enterprise_installation.when-9418-necessary %} |
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Email ports
+## 电子邮件端口
 
-Email ports must be accessible directly or via relay for inbound email support for end users.
+电子邮件端口必须可直接访问或通过中继访问，以便为最终用户提供入站电子邮件支持。
 
-| Port | Service | Description |
+| 端口 | 服务 | 说明 |
 |---|---|---|
-| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
+| 25 | SMTP | 支持采用加密的 SMTP (STARTTLS)。 |
 
-## {% data variables.product.prodname_actions %} ports
+## {% data variables.product.prodname_actions %} 端口
 
-{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)."
+{% data variables.product.prodname_actions %} 端口必须可供自托管运行器访问才能连接到 {% data variables.location.product_location %}。 有关详细信息，请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)。
 
-| Port | Service | Description |
+| 端口 | 服务 | 说明 |
 |---|---|---|
-| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured.
-| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured.
+| 443 | HTTPS | 自托管运行器连接到 {% data variables.location.product_location %} 以接收作业分配并下载新版本的运行器应用程序。 如果配置了 TLS 则必填。
+| 80 | HTTP | 自托管运行器连接到 {% data variables.location.product_location %} 以接收作业分配并下载新版本的运行器应用程序。 如果未配置 TLS 则必填。
 
-If you enable automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, {% data variables.product.prodname_actions %} will always search for an action on {% data variables.location.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)."
+如果启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问，{% data variables.product.prodname_actions %} 将始终先通过这些端口搜索 {% data variables.location.product_location %} 上的操作，然后再检查 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息，请参阅“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)。”
 
-## {% data variables.product.prodname_github_connect %} ports
+## {% data variables.product.prodname_github_connect %} 端口
 
-If you enable {% data variables.product.prodname_github_connect %}, the connection between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %} uses HTTPS over ports 443 or 80, and TLS is required. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
+如果启用 {% data variables.product.prodname_github_connect %}，则 {% data variables.product.product_name %} 和 {% data variables.product.prodname_dotcom_the_website %} 之间的连接使用 HTTPS 通过端口 443 或 80，并且需要 TLS。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)”。
 
-## Further reading
+## 延伸阅读
 
-- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)"
+- “[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)”

translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md

@@ -1,7 +1,7 @@
 ---
-title: About {% data variables.product.prodname_emus %}
+title: '关于 {% data variables.product.prodname_emus %}'
 shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+intro: '可以从标识提供者的 {% data variables.product.prodname_dotcom %} 上集中管理企业成员的标识和访问。'
 redirect_from:
   - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
@@ -17,50 +17,55 @@ topics:
   - Enterprise
   - SSO
 allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 82a8b8c29ea38d57f0481146f2a857c2dcba8413
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160726'
 ---
+## 关于 {% data variables.product.prodname_emus %}
 
-## About {% data variables.product.prodname_emus %}
+使用 {% data variables.product.prodname_emus %}，可以通过标识提供者 (IdP) 控制企业成员的用户帐户。 IdP 中分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将会预配为 {% data variables.product.prodname_dotcom %} 上的新用户帐户，并添加到企业中。 可以通过 IdP 控制用户帐户的用户名、配置文件数据、团队成员身份和存储库访问权限。
 
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
-
-In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+在 IdP 中，你可以为每个 {% data variables.enterprise.prodname_managed_user %} 提供用户、企业所有者或计费管理员的角色。 {% data variables.enterprise.prodname_managed_users_caps %} 可以拥有企业内的组织，并且可以将其他 {% data variables.enterprise.prodname_managed_users %} 添加到组织和其中的团队。 有关详细信息，请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”和“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
 
 {% ifversion oidc-for-emu %}
 
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %} 有关详细信息，请参阅“[关于对 IdP 的条件访问策略的支持](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)”。
 
 {% endif %}
 
-You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
+可以授予 {% data variables.enterprise.prodname_managed_users %} 访问权限以及参与企业内部存储库的能力，但 {% data variables.enterprise.prodname_managed_users %} 无法创建公共内容，也不能与其他用户、组织和企业协作处理 {% data variables.product.prodname_dotcom %} 的其余部分。 有关详细信息，请参阅“[{% data variables.enterprise.prodname_managed_users %} 的功能和限制](#abilities-and-restrictions-of-enterprise-managed-users)”。
 
-The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+企业的 {% data variables.enterprise.prodname_managed_users %} 的用户名及其个人资料信息（例如显示名称和电子邮件地址）通过 IdP 设置，用户无法自行更改。 有关详细信息，请参阅“[用户名和个人资料信息](#usernames-and-profile-information)”。
 
-Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
+企业所有者可以在 {% data variables.product.prodname_dotcom %} 上审核所有 {% data variables.enterprise.prodname_managed_users %} 的操作。 有关详细信息，请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)”。
 
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+若要使用 {% data variables.product.prodname_emus %}，需要启用了 {% data variables.product.prodname_emus %} 的单独企业帐户类型。 有关创建此帐户的详细信息，请参阅“[关于具有托管用户的企业](#about-enterprises-with-managed-users)”。
 
 {% note %}
 
-**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
+注意：使用 {% data variables.product.prodname_ghe_cloud %} 进行标识和访问管理有多个选项，而 {% data variables.product.prodname_emus %} 并不是每个客户的最佳解决方案。 如需详细了解 {% data variables.product.prodname_emus %} 是否适合你的企业，请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)”。
 
 {% endnote %}
 
-## About organization membership management
+## 关于组织成员身份管理
 
-Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+可手动管理组织成员身份，也可使用 IdP 组自动更新成员身份。 要通过 IdP 管理组织成员身份，必须将成员添加到 IdP 组，并且 IdP 组必须连接到组织内的团队。 有关自动管理组织和团队成员身份的详细信息，请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。
 
-The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization. 
+将成员添加到企业拥有的组织的方式（通过 IdP 组或手动）决定了必须如何从组织中删除他们。 
 
-- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
-- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+- 如果将成员手动添加到组织，则必须手动将其删除。 从 IdP 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序中取消分配他们，将暂停用户，但不会将其从组织中删除。
+- 如果用户由于被添加到映射到组织中的一个或多个团队的 IdP 组而成为该组织的成员，则从与组织关联的所有映射的 IdP 组中删除这些用户会将其从组织中删除。
 
-To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+要了解成员是如何添加到组织中的，可以按类型筛选成员列表。 有关详细信息，请参阅[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)。
 
-## Identity provider support
+## 标识提供者支持
 
-{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
+{% data variables.product.prodname_emus %} 支持以下 IdP{% ifversion oidc-for-emu %} 和身份验证方法：
 
-|                                  | SAML                                          | OIDC (beta)                                   |
+|                                  | SAML                                          | OIDC（beta 版本）                                   |
 |----------------------------------|-----------------------------------------------|-----------------------------------------------|
 | Azure Active Directory           | {% octicon "check" aria-label="Check icon" %} | {% octicon "check" aria-label="Check icon" %} |
 | Okta                             | {% octicon "check" aria-label="Check icon" %} |                                               |
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
 
 {% endif %}
 
-## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
+## {% data variables.enterprise.prodname_managed_users %} 的功能和限制
 
-{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
+{% data variables.enterprise.prodname_managed_users_caps %} 只能参与企业中的专用和内部存储库及其用户帐户拥有的专用存储库。 {% data variables.enterprise.prodname_managed_users_caps %} 对更广泛的 {% data variables.product.prodname_dotcom %} 社区具有只读访问权限。 这些针对用户和内容的可见性和访问限制适用于所有请求，包括 API 请求。
 
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises. 
-* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. 
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
-* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
-* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
+* 不能邀请 {% data variables.enterprise.prodname_managed_users_caps %} 加入企业外部的组织或存储库，也不能邀请 {% data variables.enterprise.prodname_managed_users %} 加入其他企业。 
+* {% data variables.product.prodname_emus %} 不支持外部协作者。
+* {% data variables.enterprise.prodname_managed_users_caps %} 无法在企业外部的存储库中创建问题或拉取请求、添加评论或添加反应，也不能加注星标、监视或创建分支。
+* {% data variables.enterprise.prodname_managed_users_caps %} 可以查看 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共存储库，但无法将代码推送到企业外部的存储库。
+* {% data variables.enterprise.prodname_managed_users_caps %} 和创建的内容只对企业的其他成员可见。 
+* {% data variables.enterprise.prodname_managed_users_caps %} 无法关注企业外部的用户。
+* {% data variables.enterprise.prodname_managed_users_caps %} 无法创建 Gist 或对 Gist 添加评论。
+* {% data variables.enterprise.prodname_managed_users_caps %} 无法为 {% data variables.product.prodname_actions %} 创建入门工作流。
+* {% data variables.enterprise.prodname_managed_users_caps %} 无法在其用户帐户上安装 {% data variables.product.prodname_github_apps %}。
+* 其他 {% data variables.product.prodname_dotcom %} 用户无法查看、提及或邀请 {% data variables.enterprise.prodname_managed_user %} 进行协作。
+* 可以选择 {% data variables.enterprise.prodname_managed_users %} 是否能够创建其用户帐户拥有的存储库。 有关详细信息，请参阅“[在企业中实施存储库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。
+* 如果允许 {% data variables.enterprise.prodname_managed_users %} 创建其用户帐户拥有的存储库，则他们只能拥有专用存储库，并且只能邀请其他企业成员协作处理其用户拥有的存储库。
 * {% data reusables.enterprise-accounts.emu-forks %}
-* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. 
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+* 只能在 {% data variables.enterprise.prodname_emu_enterprise %} 拥有的组织中创建专用和内部存储库，具体取决于组织和企业存储库可见性设置。 
+* {% data variables.enterprise.prodname_managed_users_caps %} 在使用 {% data variables.product.prodname_pages %} 方面受到限制。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)”。
 * {% data reusables.copilot.emus-cannot-use-copilot %}
 
-## Getting started with {% data variables.product.prodname_emus %}
+## {% data variables.product.prodname_emus %} 入门
 
-Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
+必须先执行一系列配置步骤，开发人员才能将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_emus %} 一起使用。
 
-1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+1. 若要使用 {% data variables.product.prodname_emus %}，需要启用了 {% data variables.product.prodname_emus %} 的单独企业帐户类型。 若要试用 {% data variables.product.prodname_emus %} 或讨论从现有企业迁移的选项，请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。
   
-  Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+  GitHub 销售团队的联系人将与你合作创建新的 {% data variables.enterprise.prodname_emu_enterprise %}。 你需要为将设置企业的用户提供电子邮件地址，以及一个短代码，该代码将用作企业成员用户名的后缀。 {% data reusables.enterprise-accounts.emu-shortcode %} 有关详细信息，请参阅“[用户名和个人资料信息](#usernames-and-profile-information)”。
   
-2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`. 
+2. 创建企业后，你将收到来自 {% data variables.product.prodname_dotcom %} 的电子邮件，邀请你为企业的设置用户选择密码，该用户将是企业的第一个所有者。 设置密码时，请使用隐身或专用浏览窗口。 设置用户仅用于为企业配置单一登录和 SCIM 预配集成。 成功启用 SSO 后，设置用户将不再有权管理企业帐户。 设置用户的用户名是企业的短代码，后缀为 `_admin`。 
   
   {% note %}
   
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
   
   {% endnote %}
   
-3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+3. 你以设置用户身份登录后，我们建议你启用双因素身份验证。 有关详细信息，请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。
 
-1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). Both options provide a seamless sign-in experience for your members, but only OIDC includes support for Conditional Access Policies (CAP). If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
+1. 首先，请配置 {% ifversion oidc-for-emu %} 成员如何进行身份验证。 如果使用 Azure Active Directory 作为标识提供者，可以在 OpenID Connect (OIDC) 和安全断言标记语言 (SAML) 之间进行选择。 这两个选项都为成员提供无缝登录体验，但只有 OIDC 包括对条件访问策略 (CAP) 的支持。 如果使用 Okta 作为标识提供者，则可以使用 SAML 对成员进行身份验证。{% else %}SAML SSO 适用于企业。 有关详细信息，请参阅“[为 Enterprise 托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。{% endif %}
   
   {% ifversion oidc-for-emu %}
   
-  To get started, read the guide for your chosen authentication method.
+  首先，请阅读所选身份验证方法的指南。
   
-    - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
-    - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+    - “[为企业托管用户配置 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)”。
+    - “[为企业托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。
   
   {% endif %}
   
-4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+4. 配置 SSO 后，可以配置 SCIM 预配。 SCIM 是标识提供者在 {% data variables.product.prodname_dotcom_the_website %} 上创建 {% data variables.enterprise.prodname_managed_users %} 的方式。 有关配置 SCIM 预配的详细信息，请参阅“[为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。
   
-5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
+5. 配置身份验证和预配后，可以通过将 IdP 组与团队同步来开始管理 {% data variables.enterprise.prodname_managed_users %} 的组织成员身份。 有关详细信息，请参阅[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)。
 
-If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+如果企业成员必须使用一个工作站同时从 {% data variables.enterprise.prodname_managed_user %} 和个人帐户参与 {% data variables.location.product_location %} 上的存储库，则可以提供支持。 有关详细信息，请参阅“[支持在 {% data variables.product.prodname_dotcom_the_website %} 上具有多个用户帐户的开发人员](#supporting-developers-with-multiple-user-accounts-on-githubcom)”。
 
-## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
+## 作为 {% data variables.enterprise.prodname_managed_user %} 进行身份验证
 
-{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. 
+{% data variables.enterprise.prodname_managed_users_caps %} 必须通过其标识提供者进行身份验证。 若要进行身份验证，{% data variables.enterprise.prodname_managed_user %} 可以访问其 IdP 应用程序门户或使用 {% data variables.product.prodname_dotcom_the_website %} 上的登录页。 
 
-By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
+默认情况下，当未经身份验证的用户尝试访问使用 {% data variables.product.prodname_emus %} 的企业时，{% data variables.product.company_short %} 会显示 404 错误。 企业所有者可以选择性地启用自动重定向到单一登录 (SSO)，而不会显示 404。 有关详细信息，请参阅“[为企业中的安全设置强制实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)”。
 
-{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
+{% data reusables.enterprise-accounts.about-recovery-codes %} 有关详细信息，请参阅“[管理企业的恢复代码](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)”。
 
-### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
+### 通过 {% data variables.product.prodname_dotcom_the_website %} 作为 {% data variables.enterprise.prodname_managed_user %} 进行身份验证
 
-1. Navigate to [https://github.com/login](https://github.com/login).
-1. In the "Username or email address" text box, enter your username including the underscore and short code.
-  ![Screenshot showing login form](/assets/images/help/enterprises/emu-login-username.png)
-  When the form recognizes your username, the form will update. You do not need to enter your password on this form.
-1. To continue to your identity provider, click **Sign in with your identity provider**.
-  ![Screenshot showing "Sign in with your identity provider" button](/assets/images/help/enterprises/emu-login-submit.png)
+1. 导航到 [https://github.com/login](https://github.com/login)。
+1. 在“用户名或电子邮件地址”文本框中，输入用户名，包括下划线和短代码。
+  ![显示登录表单的屏幕截图](/assets/images/help/enterprises/emu-login-username.png) 表单识别用户名后将更新。 无需在此表单中输入密码。
+1. 若要继续访问标识提供者，请单击“使用标识提供者登录”。
+  ![显示“使用标识提供者登录”按钮的屏幕截图](/assets/images/help/enterprises/emu-login-submit.png)
 
-## Usernames and profile information
+## 用户名和个人资料信息
 
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+{% data variables.product.product_name %} 通过规范 IdP 提供的标识符自动为每个用户创建用户名。 有关详细信息，请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。
 
-A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
+如果在规范化期间删除 IdP 提供的标识符的唯一部分，则预配用户时可能会发生冲突。 如果由于用户名冲突而无法预配用户，则应修改 IdP 提供的用户名。 有关详细信息，请参阅“[解决用户名问题](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)”。
 
 {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} 
 
-The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
+IdP 还提供了 {% data variables.enterprise.prodname_managed_user %} 的个人资料名称和电子邮件地址。 {% data variables.enterprise.prodname_managed_users_caps %} 无法更改 {% data variables.product.prodname_dotcom %} 上的个人资料名称或电子邮件地址，并且 IdP 仅可提供单个电子邮件地址。
 
-## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
+## 支持在 {% data variables.location.product_location %} 上具有多个用户帐户的开发人员
 
-People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
+团队中的人员可能需要在 {% data variables.location.product_location %} 上参与 {% data variables.enterprise.prodname_emu_enterprise %} 外部的资源。 例如，你可能希望为公司的开放源代码项目维护单独的企业。 由于 {% data variables.enterprise.prodname_managed_user %} 无法参与公共资源，因此用户需要为此工作维护单独的个人帐户。
 
-People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+必须使用一个工作站在 {% data variables.location.product_location %} 上从两个用户帐户进行参与的人员可以配置 Git 以简化该过程。 有关详细信息，请参阅“[管理多个帐户](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)”。

translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md

@@ -1,7 +1,7 @@
 ---
-title: Configuring SCIM provisioning for Enterprise Managed Users with Okta
+title: 使用 Okta 为企业托管用户配置 SCIM 预配
 shortTitle: Set up provisioning with Okta
-intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider.
+intro: 您可以使用 Okta 作为身份提供商来预配新用户并管理其企业和团队的成员身份。
 product: '{% data reusables.gated-features.emus %}'
 versions:
   ghec: '*'
@@ -17,81 +17,86 @@ topics:
   - Authentication
   - Enterprise
   - SSO
+ms.openlocfilehash: b8c086d1d91c1248fa5a0349bb6f8ef32c3bbdf0
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160710'
 ---
+## 关于使用 Okta 进行预配
 
-## About provisioning with Okta
+您可以使用 {% data variables.product.prodname_emus %} Okta 作为您的身份提供商来预配新帐户、管理企业成员身份以及管理企业中组织的团队成员身份。 有关预配 {% data variables.product.prodname_emus %} 的详细信息，请参阅“[为 Enterprise Managed User 配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。
 
-You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+在使用 Okta 配置预配之前，必须配置 SAML 单点登录。 有关详细信息，请参阅“[为 Enterprise Managed User 配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。
 
-Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+要使用 Okta 配置预配，必须在 {% data variables.product.prodname_emu_idp_application %} 应用程序中设置企业名称，并输入安装用户的 {% data variables.product.pat_generic %}。 然后，您可以在 Okta 中开始预配用户。
 
-To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta.
+## 支持的功能
 
-## Supported features
+{% data variables.product.prodname_emus %} 支持 Okta 中的许多预配功能。
 
-{% data variables.product.prodname_emus %} supports many provisioning features in Okta.
-
-| Feature | Description |
+| 功能 | 说明 |
 | --- | --- |
-| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. |
-| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. |
-| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. |
-| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. |
-| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. |
+| 推送新用户 | 分配给 Okta 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将在 {% data variables.product.product_name %} 上自动创建。 |
+| 推送配置文件更新 | 对 Okta 中的用户配置文件所做的更新将被推送到 {% data variables.product.product_name %}。 |
+| 推送组 | Okta 中作为推送组分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的组将在 {% data variables.product.product_name %} 上自动创建。 |
+| 推送用户停用 | 从 Okta 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序中取消分配用户将在 {% data variables.product.product_name %} 上禁用该用户。 用户将无法登录，但会保留用户的信息。 |
+| 重新激活用户 | 将启用 Okta 中已重新激活其 Okta 帐户并将其分配回 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户。 |
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames.
+**注意：** {% data variables.product.prodname_emus %} 不支持修改用户名。
 
 {% endnote %}
 
-## Setting your enterprise name
+## 设置企业名称
 
-After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta.
+创建 {% data variables.enterprise.prodname_emu_enterprise %} 后，可以通过在 Okta 中设置企业名称来开始配置预配。
 
-1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
-1. Click the **Sign On** tab.
-1. To make changes, click **Edit**.
-1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc".
-![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png)
-1. To save your enterprise name, click **Save**.
+1. 导航到 Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。
+1. 单击“登录”选项卡。
+1. 若要进行更改，请单击“编辑”。
+1. 在“Advanced Sign-on Settings（高级登录设置）”下的“Enterprise Name（企业名称）”文本框中，键入您的企业名称。 例如，如果你在 `https://github.com/enterprises/octoinc` 访问你的企业，则你的企业名称将为“octoinc”。
+![Okta 上的“企业名称”字段的屏幕截图](/assets/images/help/enterprises/okta-emu-enterprise-name.png)
+1. 若要保存企业名称，请单击“保存”。
 
-## Configuring provisioning
+## 配置预配
 
-After setting your enterprise name, you can proceed to configure provisioning settings.
+设置企业名称后，可以继续配置预配设置。
 
-To configure provisioning, the setup user with the **@<em>SHORT-CODE</em>_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)."
+若要配置预配，具有 @SHORT-CODE_admin 用户名的安装用户将需要提供作用域为 admin:enterprise 的 {% data variables.product.pat_v1 %}。 有关创建新令牌的详细信息，请参阅“[创建 {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)”。
 
-1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta.
-1. Click the **Provisioning** tab.
-1. In the settings menu, click **Integration**.
-1. To make changes, click **Edit**.
-1. Select **Enable API integration**.
-1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user.
-![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png)
-1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen.
-1. To save the token, click **Save**.
-1. In the settings menu, click **To App**.
-![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png)
-1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**.
-1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**.
-![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png)
-1. To finish configuring provisioning, click **Save**.
+1. 导航到 Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。
+1. 单击 **资源调配** 选项卡。
+1. 在“设置”菜单中，单击“集成”。
+1. 若要进行更改，请单击“编辑”。
+1. 选择“启用 API 集成”。
+1. 在“API 令牌”字段中，输入属于安装用户的作用域为 admin:enterprise 的 {% data variables.product.pat_v1 %}。
+![显示 Okta 上的 API 令牌字段的屏幕截图](/assets/images/help/enterprises/okta-emu-token.png)
+1. 单击“测试 API 凭据”。 如果测试成功，屏幕顶部将显示一条验证消息。
+1. 若要保存令牌，请单击“保存”。
+1. 在“设置”菜单中，单击“转到应用”。
+![显示 Okta 上的“转到应用”菜单项的屏幕截图](/assets/images/help/enterprises/okta-emu-to-app-menu.png)
+1. 在“预配到应用”的右侧，要允许进行更改，请单击“编辑”。
+1. 对于“创建用户”、“更新用户属性”和“停用用户”，选择“启用”   。
+![显示 Okta 上的预配选项的屏幕截图](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png)
+1. 若要完成配置预配，请单击“保存”。
 
-## Assigning users and groups
+## 分配用户和组
 
-After you have configured SAML SSO and provisioning, you will be able to provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users or groups to the {% data variables.product.prodname_emu_idp_application %} application. 
+配置 SAML SSO 和预配后，可以通过将用户或组分配到 {% data variables.product.prodname_emu_idp_application %} 应用程序在 {% data variables.product.prodname_dotcom_the_website %} 上预配新用户。 
 
 {% data reusables.scim.emu-scim-rate-limit %}
 
-You can also automatically manage organization membership by adding groups to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+还可以通过将组添加到 Okta 中的“推送组”选项卡来自动管理组织成员身份。 成功预配组后，该组将可用于连接到企业组织中的团队。 有关管理团队的详细信息，请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。
 
-When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+分配用户时，可以使用 {% data variables.product.prodname_emu_idp_application %} 应用程序中的“角色”属性在 {% data variables.product.product_name %} 上设置用户在企业中的角色。 有关角色的详细信息，请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”。
 
-![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png)
+![显示 Okta 上已预配用户的角色选项的屏幕截图](/assets/images/help/enterprises/okta-emu-user-role.png)
 
-## Deprovisioning users and groups
+## 取消预配用户和组
 
-To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab.
+若要从 {% data variables.product.product_name %} 中删除用户或组，请从 Okta 的“分配”选项卡和“推送组”选项卡中删除用户或组。 对于用户，请确保从“推送组”选项卡中的所有组中删除该用户。
 
 

translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md

@@ -1,7 +1,7 @@
 ---
-title: Managing team memberships with identity provider groups
+title: 使用标识提供者组管理团队成员身份
 shortTitle: Manage teams with your IdP
-intro: 'You can manage team and organization membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with teams within your {% data variables.enterprise.prodname_emu_enterprise %}.'
+intro: '将 IdP 组与 {% data variables.enterprise.prodname_emu_enterprise %} 中的团队连接，可以通过标识提供者 (IdP) 管理 {% data variables.product.product_name %} 上的团队和组织成员身份。'
 product: '{% data reusables.gated-features.emus %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups
@@ -16,77 +16,74 @@ topics:
   - Enterprise
   - SSO
   - Teams
+ms.openlocfilehash: 179835d6642cd5718a565869337b5420b29407a5
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160822'
 ---
+## 关于使用 {% data variables.product.prodname_emus %} 的团队管理
 
-## About team management with {% data variables.product.prodname_emus %}
+使用 {% data variables.product.prodname_emus %}，可以通过将 {% data variables.product.prodname_dotcom %} 团队与 IdP 组连接起来，通过 IdP 管理企业内的团队和组织成员身份。 将某个企业组织中的团队连接到 IdP 组时，IdP 组对成员身份的更改会自动反映在企业中，从而减少手动更新和自定义脚本的需要。 
 
-With {% data variables.product.prodname_emus %}, you can manage team and organization membership within your enterprise through your IdP by connecting {% data variables.product.prodname_dotcom %} teams with IdP groups. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. 
-
-When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means.
+当 IdP 组的更改或新的团队连接导致 {% data variables.enterprise.prodname_managed_user %} 加入他们尚未加入的组织中的团队时，{% data variables.enterprise.prodname_managed_user %} 将自动添加到组织中。 当你断开组与团队的连接时，如果未通过任何其他方式为其分配组织成员身份，则通过团队成员身份成为组织成员的用户将从组织中删除。
 
 {% note %}
 
-**Note:** Organization owners can also add {% data variables.enterprise.prodname_managed_users %} to organizations manually, as long as the accounts have already been provisioned via SCIM.
+注意：组织所有者也可以手动将 {% data variables.enterprise.prodname_managed_users %} 添加到组织，只要帐户已通过 SCIM 进行预配。
 
 {% endnote %}
 
-When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning.
+当 Idp 上的组成员身份发生变化时，你的 IdP 会根据 IdP 确定的时间表发送 SCIM 请求，其中包含对 {% data variables.product.prodname_dotcom_the_website %} 的更改，因此更改可能不会立即发生。 任何更改团队或组织成员身份的请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。
 
-Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team.
+连接到 IdP 组的团队不能是其他团队的父级，也不能是另一个团队的子级。 如果要连接到 IdP 组的团队是父团队或子团队，建议创建一个新团队或删除使你的团队成为父团队的嵌套关系。
 
-To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
+若要管理企业中任何团队（包括连接到 IdP 组的团队）的存储库访问权限，必须对 {% data variables.product.prodname_dotcom_the_website %} 进行更改。 有关详细信息，请参阅“[管理团队对组织存储库的访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。
 
-## Requirements for connecting IdP groups with teams
+## 将 IdP 组与团队连接的要求
 
-Before you can connect an IdP group with a team on {% data variables.product.prodname_dotcom %}, you must assign the group to the {% data variables.product.prodname_emu_idp_application %} application in your IdP. For more information, see "[About SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)."
+在将 IdP 组与 {% data variables.product.prodname_dotcom %} 上的团队连接之前，必须将该组分配给 IdP 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_emus %} 的 SCIM 预配](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)”。
 
-You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise.
+可以将企业中的团队连接到一个 IdP 组。 可以将同一 IdP 组分配给企业中的多个团队。
 
-If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}.
+如果要将现有团队连接到 IdP 组，必须先删除手动添加的任何成员。 将企业中的团队连接到 IdP 组后，IdP 管理员必须通过标识提供者更改团队成员身份。 无法在 {% data variables.product.prodname_dotcom_the_website %} 上管理团队成员身份。
 
-## Creating a new team connected to an IdP group
+## 创建连接到 IdP 组的新团队
 
-Any member of an organization can create a new team and connect the team to an IdP group. 
+组织的任何成员都可以创建新团队并将团队连接到 IdP 组。 
 
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.new_team %}
-{% data reusables.organizations.team_name %}
-{% data reusables.organizations.team_description %}
-1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
-{% data reusables.organizations.team_visibility %}
-{% data reusables.organizations.create_team %}
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %}
+1. 若要连接团队，请选择“标识提供者组”下拉菜单，然后单击要连接的团队。
+    ![用于选择标识提供者组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png) {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %}
 
-## Managing the connection between an existing team and an IdP group
+## 管理现有团队和 IdP 组之间的连接
 
-Organization owners and team maintainers can manage the existing connection between an IdP group and a team.
+组织所有者和团队维护者可以管理 IdP 组和团队之间的现有连接。
 
 {% note %}
 
-**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)."
+注意：在首次将 {% data variables.product.prodname_dotcom_the_website %} 上的现有团队连接到 IdP 组之前，必须先删除 {% data variables.product.prodname_dotcom_the_website %} 上的所有团队成员。 有关详细信息，请参阅“[从团队中删除组织成员](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)”。
 
 {% endnote %}
 
 {% data reusables.profile.access_profile %}
 
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.specific_team %}
-{% data reusables.organizations.team_settings %}
-1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
-1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
-1. Click **Save changes**.
+{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
+1. （可选）在“标识提供者组”下，单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 
+    ![从 GitHub 团队取消选择已连接的 IdP 组](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
+1. 若要连接 IdP 组，请在“标识提供者组”下选择下拉菜单，然后从列表中单击标识提供者组。
+    ![用于选择标识提供者组的下拉菜单](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+1. 单击“保存更改”。 
 
-## Viewing IdP groups, group membership, and connected teams
+## 查看 IdP 组、组成员身份和连接的团队
 
-You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP.
+可以查看 IdP 组列表，查看连接到 IdP 组的任何团队，并在 {% data variables.product.product_name %} 上查看每个 IdP 组的成员身份。 必须在 IdP 上编辑组的成员身份。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**.
-    ![Screenshot showing "Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png)
-2. To see the members and teams connected to an IdP group, click the group's name.
-    ![Screenshot showing list of IdP groups, the group name is highlighted](/assets/images/help/enterprises/select-idp-group.png)
-4. To view the teams connected to the IdP group, click **Teams**. 
-    ![Screenshot showing the "Teams" button](/assets/images/help/enterprises/idp-groups-team-switcher.png)
+1. 若要查看 IdP 组列表，请在左侧边栏中单击 {% octicon "key" aria-label="The key icon" %}“标识提供者”。
+    ![显示企业侧栏中“标识提供者”选项卡的屏幕截图](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png)
+2. 若要查看连接到 IdP 组的成员和团队，请单击该组的名称。
+    ![显示 IdP 组列表的屏幕截图，其中突出显示了组名称](/assets/images/help/enterprises/select-idp-group.png)
+4. 若要查看连接到 IdP 组的团队，请单击“团队”。 
+    ![显示“团队”按钮的屏幕截图](/assets/images/help/enterprises/idp-groups-team-switcher.png)

translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md

@@ -18,7 +18,7 @@ topics:
 
 ## Using the audit log API
 
-You can interact with the audit log using the GraphQL API or the REST API. 
+You can interact with the audit log using the GraphQL API or the REST API.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
 
 Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
 

translations/zh-CN/content/admin/overview/index.md

@@ -19,11 +19,11 @@ children:
   - /best-practices-for-enterprises
   - /creating-an-enterprise-account
   - /accessing-compliance-reports-for-your-enterprise
-ms.openlocfilehash: d936542993310333e314efcc9d5bb5689be00701
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f0322eef087f09b029051fc08ac61bc4e529d6dc
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147389841'
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163554'
 ---
 如需更多信息或购买 {% data variables.product.prodname_enterprise %}，请参阅 [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise)。

translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md

@@ -1,7 +1,7 @@
 ---
-title: Configuring the CodeQL workflow for compiled languages
+title: 为编译的语言配置 CodeQL 工作流
 shortTitle: Configure compiled languages
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.code-scanning.codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
+intro: '可以配置 {% data variables.product.prodname_dotcom %} 如何使用 {% data variables.code-scanning.codeql_workflow %} 扫描用编译语言编写的代码以查找漏洞和错误。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
 redirect_from:
@@ -25,107 +25,106 @@ topics:
   - C/C++
   - C#
   - Java
+ms.openlocfilehash: 91983e79a6381b4a38cbb1de4f6d7f228637b192
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161197'
 ---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
+## 关于 {% data variables.code-scanning.codeql_workflow %} 和编译语言
 
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
+通过添加 {% data variables.product.prodname_actions %} 工作流程到仓库，设置 {% data variables.product.prodname_dotcom %} 对仓库运行 {% data variables.product.prodname_code_scanning %}。 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，可以添加 {% data variables.code-scanning.codeql_workflow %}。 有关详细信息，请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。
 
-## About the {% data variables.code-scanning.codeql_workflow %} and compiled languages
+{% data reusables.code-scanning.edit-workflow %} 有关配置 {% data variables.product.prodname_code_scanning %} 和编辑工作流文件的一般信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %} ](/code-security/secure-coding/configuring-code-scanning)”和“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.code-scanning.codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+##  关于 {% data variables.product.prodname_codeql %} 的自动构建
 
-{% data reusables.code-scanning.edit-workflow %} 
-For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and  "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
-
-##  About autobuild for {% data variables.product.prodname_codeql %}
-
-{% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.   
-For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
+{% data variables.product.prodname_code_scanning_capc %} 的工作原理是针对一个或多个数据库运行查询。 每个数据库都包含仓库中所有代码的单一语言表示形式。   
+对于编译语言 C/C++、C#、{% ifversion codeql-go-autobuild %} Go、{% endif %} 和 Java，填充此数据库的过程涉及构建代码和提取数据。 {% data reusables.code-scanning.analyze-go %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %}
 
-If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
+如果你的工作流使用 `language` 矩阵，`autobuild` 会尝试生成矩阵中列出的每种编译语言。 如果不使用矩阵，则 `autobuild` 会尝试生成在存储库中具有最多源文件的受支持编译语言。 除 Go 以外，除非您提供明确的构建命令，否则您仓库中其他编译语言的分析将失败。
 
 {% note %}
 
-{% ifversion ghae %}
-**Note**: {% data reusables.actions.self-hosted-runners-software %}
-{% else %}
-**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% ifversion ghae %} **注意**：{% data reusables.actions.self-hosted-runners-software %} {% else %} **注意**：如果使用 {% data variables.product.prodname_actions %} 的自承载运行器，则可能需要安装其他软件才能使用 `autobuild` 进程。 此外，如果您的仓库需要特定版本的构建工具，您可能需要手动安装它。 有关详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
 {% endif %}
 
 {% endnote %}
 
 ### C/C++
 
-| Supported system type | System name |
+| 支持的系统类型 | 系统名称 |
 |----|----|
-| Operating system | Windows, macOS, and Linux |
-| Build system | Windows: MSbuild and build scripts<br/>Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
+| 操作系统 | Windows、macOS 和 Linux |
+| 构建系统 | Windows：MSbuild 和生成脚本<br/>Linux 和 macOS：Autoconf、Make、CMake、qmake、Meson、Waf、SCons、Linux Kbuild 和生成脚本 |
 
-The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
+`autobuild` 步骤的行为因运行提取的操作系统而异。 在 Windows 上，`autobuild` 步骤尝试使用以下方法自动检测适合 C/C++ 的生成方法：
 
-1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root.
-If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
+1. 对离根最近的解决方案 (`.sln`) 或项目 (`.vcxproj`) 文件调用 `MSBuild.exe`。
+如果 `autobuild` 在顶层目录下的相同（最短）深度检测到多个解决方案或项目文件，它将尝试生成所有这些文件。
+2. 调用看起来像生成脚本的脚本：build.bat、build.cmd 和 build.exe（按此顺序）  。
 
-On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
+在 Linux 和 macOS 上，`autobuild` 步骤检查存储库中存在的文件，以确定使用的生成系统：
 
-1. Look for a build system in the root directory.
-2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
-3. Run an appropriate command to configure the system. 
+1. 在根目录中查找构建系统。
+2. 如果未找到，则搜索子目录以查找含有 C/C++ 构建系统的唯一目录。
+3. 运行适当的命令来配置系统。 
 
 ### C#
 
-| Supported system type | System name |
+| 支持的系统类型 | 系统名称 |
 |----|----|
-| Operating system | Windows and Linux |
-| Build system | .NET and MSbuild, as well as build scripts |
+| 操作系统 | Windows 和 Linux |
+| 构建系统 | .NET 和 MSbuild，以及构建脚本 |
 
-The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
+`autobuild` 进程尝试使用以下方法自动检测适合 C# 的构建方法：
 
-1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
-2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root.
-If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
+1. 对离根最近的解决方案 (`.sln`) 或项目 (`.csproj`) 文件调用 `dotnet build`。
+2. 对离根最近的解决方案或项目文件调用 `MSbuild` (Linux) 或 `MSBuild.exe` (Windows)。
+如果 `autobuild` 在顶层目录下的相同（最短）深度检测到多个解决方案或项目文件，它将尝试生成所有这些文件。
+3. 调用看起来像生成脚本的脚本：build 和 build.sh（对于 Linux，按此顺序）或 build.bat、build.cmd 和 build.exe（对于 Windows，按此顺序）    。
 
 {% ifversion codeql-go-autobuild %}
 
 ### Go
 
-| Supported system type | System name |
+| 支持的系统类型 | 系统名称 |
 |----|----|
-| Operating system | Windows, macOS, and Linux |
-| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
+| 操作系统 | Windows、macOS 和 Linux |
+| 构建系统 | Go 模块、`dep` 和 Glide，以及生成脚本，包括 Makefiles 和 Ninja 脚本 |
 
-The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
+`autobuild` 过程尝试在提取所有 `.go` 文件之前自动检测安装 Go 存储库所需的依赖项的合适方法：
 
-1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed.
-2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies.
-3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
-4. Extract all Go code in the repository, similar to running `go build ./...`.
+1. 调用 `make`、`ninja`、`./build` 或 `./build.sh`（按该顺序），直到其中一个命令成功，后续 `go list ./...` 也成功，这表示已安装所需的依赖项。
+2. 如果这些命令都没有成功，请查找 `go.mod`、`Gopkg.toml` 或 `glide.yaml`，并分别运行 `go get`（除非正在使用供应商）、`dep ensure -v` 或 `glide install` 以尝试安装依赖项。
+3. 最后，如果未找到这些依赖项管理器的配置文件，请重新排列适合添加到 `GOPATH` 的存储库目录结构，并使用 `go get` 安装依赖项。 提取完成后，目录结构恢复为正常。
+4. 提取存储库中的所有 Go 代码，类似于运行 `go build ./...`。
 
 {% endif %}
 
 ### Java
 
-| Supported system type | System name |
+| 支持的系统类型 | 系统名称 |
 |----|----|
-| Operating system | Windows, macOS, and Linux (no restriction) |
-| Build system | Gradle, Maven and Ant |
+| 操作系统 | Windows、macOS 和 Linux（无限制） |
+| 构建系统 | Gradle、Maven 和 Ant |
 
-The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
+`autobuild` 进程尝试通过应用此策略来确定 Java 代码库的生成系统：
 
-1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
-2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
-3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
+1. 在根目录中搜索构建文件。 先后检查 Gradle、Maven 和 Ant 构建文件。
+2. 运行找到的第一个构建文件。 如果 Gradle 和 Maven 文件都存在，则使用 Gradle 文件。
+3. 否则，在根目录的直接子目录中搜索构建文件。 如果只有一个子目录包含构建文件，则运行该子目录中标识的第一个文件（使用与 1 相同的首选项）。 如果多个子目录包含构建文件，则报告错误。
 
-## Adding build steps for a compiled language
+## 添加编译语言的构建步骤
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
+{% data reusables.code-scanning.autobuild-add-build-steps %} 有关如何编辑工作流文件的信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)”。
 
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process.
+删除 `autobuild` 步骤后，取消注释 `run` 步骤并添加适合存储库的生成命令。 工作流 `run` 步骤会使用操作系统的 shell 来运行命令行程序。 可以修改这些命令并添加更多命令以自定义生成过程。
 
 ``` yaml
 - run: |
@@ -133,9 +132,9 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
     make release
 ```
 
-For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+有关 `run` 关键字的详细信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
 
-If your repository contains multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, and `autobuild` correctly builds C/C++ and C# but fails to build Java, you could use the following configuration in your workflow, after the `init` step. This specifies build steps for Java while still using `autobuild` for C/C++ and C#:
+如果存储库包含多个编译语言，可以指定特定于语言的生成命令。 例如，如果存储库包含 C/C++、C# 和 Java，而 `autobuild` 正确生成了 C/C++ 和 C#，但未能生成 Java，那么在 `init` 步骤之后，可以在工作流中使用以下配置。 这指定了 Java 的生成步骤，同时仍然为 C/C++ 和 C# 使用 `autobuild`：
 
 ```yaml
 - if: matrix.language == 'cpp' || matrix.language == 'csharp' 
@@ -149,8 +148,8 @@ If your repository contains multiple compiled languages, you can specify languag
     make release
 ```
 
-For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
+有关 `if` 条件的详细信息，请参阅“[GitHub Actions 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)”。
 
-For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
+有关为什么 `autobuild` 无法生成代码的更多提示和技巧，请参阅“[{% data variables.product.prodname_codeql %} 工作流故障排除](/code-security/secure-coding/troubleshooting-the-codeql-workflow)”。
 
-If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
+如果您为编译语言添加了手动构建步骤，但 {% data variables.product.prodname_code_scanning %} 仍然无法处理您的仓库，请联系 {% data variables.contact.contact_support %}。

translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md

@@ -1,5 +1,5 @@
 ---
-title: Uploading a SARIF file to GitHub
+title: 将 SARIF 文件上传到 GitHub
 shortTitle: Upload a SARIF file
 intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}'
 permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.'
@@ -23,54 +23,57 @@ topics:
   - Repositories
   - CI
   - SARIF
+ms.openlocfilehash: 3def104e487f54e2c48d462d1dcfe8bab63c6fa3
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161157'
 ---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
+## 关于 {% data variables.product.prodname_code_scanning %} 的 SARIF 文件上传
 
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+{% data variables.product.prodname_dotcom %} 使用静态分析结果交换格式 (SARIF) 文件中的信息创建 {% data variables.product.prodname_code_scanning %} 警报。 SARIF 文件可通过在用于上传文件的 {% data variables.product.prodname_actions %} 工作流程中运行的 SARIF 兼容分析工具生成。 或者，当文件生成为仓库外部的构件时， 您可以直接将 SARIF 文件推送到仓库，并使用工作流程上传 SARIF 文件。 有关详细信息，请参阅“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。
 
-## About SARIF file uploads for {% data variables.product.prodname_code_scanning %}
+您可以使用许多静态分析安全测试工具来生成 SARIF 文件，包括 {% data variables.product.prodname_codeql %}。 结果必须使用 SARIF 版本 2.1.0。 有关详细信息，请参阅“[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/code-security/secure-coding/sarif-support-for-code-scanning)”。
 
-{% data variables.product.prodname_dotcom %} creates {% data variables.product.prodname_code_scanning %} alerts in a repository using information from Static Analysis Results Interchange Format (SARIF) files. SARIF files can be uploaded to a repository using the API or {% data variables.product.prodname_actions %}. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+可以使用 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_code_scanning %} API{% ifversion codeql-runner-supported %} the {% data variables.code-scanning.codeql_runner %},{% endif %} 或 {% data variables.product.prodname_codeql_cli %} 上传结果。 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用：
 
-You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
-
-You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API,{% ifversion codeql-runner-supported %} the {% data variables.code-scanning.codeql_runner %},{% endif %} or the {% data variables.product.prodname_codeql_cli %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
-
-- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
-- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
- - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% ifversion codeql-runner-supported %}
-- The {% data variables.code-scanning.codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %}
-- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
+- {% data variables.product.prodname_actions %} 来运行 {% data variables.product.prodname_codeql %} 操作，则无需进一步操作。 {% data variables.product.prodname_codeql %} 操作在完成分析后自动上传 SARIF 文件。
+- {% data variables.product.prodname_actions %} 运行与 SARIF 兼容的分析工具，您可以更新工作流程以包括上传结果的最后一步（见下文）。
+ - {% data variables.product.prodname_codeql_cli %} 在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}，你可以使用 CLI 将结果上传到 {% data variables.product.prodname_dotcom %}（有关详细信息，请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”）。{% ifversion codeql-runner-supported %}
+- {% data variables.code-scanning.codeql_runner %}，要在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}，默认情况下运行器会在完成后自动将结果上传到 {% data variables.product.prodname_dotcom %}。 如果阻止自动上传，当准备好上传结果时，可以使用 `upload` 命令（有关详细信息，请参阅“[在 CI 系统中运行 {% data variables.code-scanning.codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”）。{% endif %}
+- 作为存储库外部工件生成结果的工具，你可以使用 {% data variables.product.prodname_code_scanning %} API 上传文件（有关详细信息，请参阅“[将分析作为 SARIF 数据上传](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)”）。
 
 {% data reusables.code-scanning.not-available %}
 
-## Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
+## 通过 {% data variables.product.prodname_actions %} 上传 {% data variables.product.prodname_code_scanning %} 分析
 
-To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a  workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+要使用 {% data variables.product.prodname_actions %} 将第三方 SARIF 文件上传到存储库，需要工作流程。 有关详细信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameters you'll use are:
+工作流将需要使用 `upload-sarif` 操作，该操作是 `github/codeql-action` 存储库的一部分。 它包含可用于配置上传的输入参数。 您将使用的主要输入参数是：
 
-- `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository.
-- `category` (optional), which assigns a category for results in the SARIF file. This enables you to analyze the same commit in multiple ways and review the results using the {% data variables.product.prodname_code_scanning %} views in {% data variables.product.prodname_dotcom %}. For example, you can analyze using multiple tools, and in mono-repos, you can analyze different slices of the repository based on the subset of changed files.
+- `sarif-file`，用于配置要上传的 SARIF 文件的文件或目录。 目录或文件路径相对于存储库的根目录。
+- `category`（可选），用于为 SARIF 文件中的结果分配类别。 这使您能够以多种方式分析同一提交，并使用 {% data variables.product.prodname_dotcom %} 中的 {% data variables.product.prodname_code_scanning %} 视图查看结果。 例如，您可以使用多个工具进行分析，在单存储库中，您可以根据已更改文件的子集分析存储库的不同片段。
 
-For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
+有关详细信息，请参阅 [`upload-sarif` 操作](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif)。
 
-The `upload-sarif` action can be configured to run when the `push` and `scheduled` event occur. For more information about {% data variables.product.prodname_actions %}  events, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+`upload-sarif` 操作可以配置为在 `push` 和 `scheduled` 事件发生时运行。 有关 {% data variables.product.prodname_actions %} 事件的详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。
 
-If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)."
+如果你的 SARIF 文件不包含 `partialFingerprints`，则 `upload-sarif` 操作将为你计算 `partialFingerprints` 字段并尝试防止重复警报。 仅当存储库同时包含 SARIF 文件和静态分析中使用的源代码时，{% data variables.product.prodname_dotcom %} 才能创建 `partialFingerprints`。 有关防止重复警报的详细信息，请参阅“[关于代码扫描的 SARIF 支持](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)”。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### Example workflow for SARIF files generated outside of a repository
+### 在存储库外部生成的 SARIF 文件的工作流程示例
 
-You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository.
+您可以创建一个新的工作流程，以在将 SARIF 文件提交到仓库后上传它们。 当 SARIF 文件作为存储库外部的工件生成时，这很有用。
 
-This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+只要提交被推送到仓库，此示例工作流程就会运行。 操作使用 `partialFingerprints` 属性来确定是否发生了更改。 除了在推送提交时运行，工作流计划为每周运行一次。 有关详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。
 
-This workflow uploads the `results.sarif` file located in the root of the repository. For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+此工作流上传位于存储库根目录中的 `results.sarif` 文件。 有关创建工作流文件的详细信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-Alternatively, you could modify this workflow to upload a directory of SARIF files. For example, you could place all SARIF files in a directory in the root of your repository called `sarif-output` and set the action's input parameter `sarif_file` to `sarif-output`. Note that if you upload a directory, each SARIF file must include a unique `runAutomationDetails.id` to define the category for the results. For more information, see "[`runAutomationDetails` object](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)."
+或者，您也可以修改此工作流程以上传 SARIF 文件的目录。 例如，您可以将所有 SARIF 文件放在存储库根目录中名为 `sarif-output` 的目录中，并将操作的输入参数 `sarif_file` 设置为 `sarif-output`。 请注意，如果上传目录，则每个 SARIF 文件都必须包含唯一的 `runAutomationDetails.id` 才能定义结果的类别。 有关详细信息，请参阅“[`runAutomationDetails` 对象](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)”。
 
 ```yaml
 name: "Upload SARIF"
@@ -105,13 +108,13 @@ jobs:
           category: my-analysis-tool
 ```
 
-### Example workflow that runs the ESLint analysis tool
+### 运行 ESLint 分析工具的示例工作流程
 
-If you generate your third-party SARIF file as part of a continuous integration (CI) workflow, you can add the `upload-sarif` action as a step after running your CI tests. If you don't already have a CI workflow, you can create one using a {% data variables.product.prodname_actions %} template. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+如果在持续集成 (CI) 工作流中生成第三方 SARIF 文件，则可以在运行 CI 测试后将 `upload-sarif` 操作添加为一个步骤。 如果您还没有 CI 工作流程，可以使用 {% data variables.product.prodname_actions %} 模板创建一个。 有关详细信息，请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。
 
-This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+只要提交被推送到仓库，此示例工作流程就会运行。 操作使用 `partialFingerprints` 属性来确定是否发生了更改。 除了在推送提交时运行，工作流计划为每周运行一次。 有关详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。
 
-The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+工作流程显示了将 ESLint 静态分析工具作为工作流程中一个步骤运行的示例。 `Run ESLint` 步骤运行 ESLint 工具并输出 `results.sarif` 文件。 然后，工作流使用 `upload-sarif` 操作将 `results.sarif` 文件上传到 {% data variables.product.prodname_dotcom %}。 有关创建工作流文件的详细信息，请参阅“[GitHub Actions 简介](/actions/learn-github-actions/introduction-to-github-actions)”。
 
 ```yaml
 name: "ESLint analysis"
@@ -147,9 +150,9 @@ jobs:
           sarif_file: results.sarif
 ```
 
-## Further reading
+## 延伸阅读
 
-- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"
-- "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
+- [{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions)
+- [查看工作流历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)
+- [关于 CI 系统中的 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)
+- [上传分析作为 SARIF 数据](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)

translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md

@@ -1,7 +1,7 @@
 ---
-title: Running CodeQL runner in your CI system
+title: 在 CI 系统中运行 CodeQL 运行器
 shortTitle: Run CodeQL runner
-intro: 'You can use the {% data variables.code-scanning.codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+intro: '可以使用 {% data variables.code-scanning.codeql_runner %} 在第三方持续集成系统中执行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
@@ -24,102 +24,102 @@ topics:
   - Integration
   - CI
   - SARIF
+ms.openlocfilehash: 7e60376ed165a3af2da7f000c37d326cb33ade99
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161092'
 ---
-
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% ifversion codeql-runner-supported %}
 
-{% data reusables.code-scanning.deprecation-codeql-runner %}
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About the {% data variables.code-scanning.codeql_runner %}
+## 关于 {% data variables.code-scanning.codeql_runner %}
 
-The {% data variables.code-scanning.codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
+{% data variables.code-scanning.codeql_runner %} 是可以用来在第三方持续集成 (CI) 系统中处理的代码上运行 {% data variables.product.prodname_code_scanning %} 的工具。 {% data reusables.code-scanning.about-code-scanning %} 有关信息，请参阅“[关于使用 {% data variables.product.prodname_codeql %} 进行 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)”。
 
-In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. 
+在许多情况下，在 CI 系统中直接使用 {% data variables.product.prodname_codeql_cli %} 设置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 更简单。 
 
-Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+您也可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 中运行 {% data variables.product.prodname_code_scanning %}。 有关信息，请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。
 
-The {% data variables.code-scanning.codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
+{% data variables.code-scanning.codeql_runner %} 是在 {% data variables.product.prodname_dotcom %} 存储库的签出上运行 {% data variables.product.prodname_codeql %} 分析的命令行工具。 你可以将运行器添加到第三方系统，然后调用运行器以分析代码并将结果上传到 {% data variables.product.product_name %}。 这些结果在仓库中显示为 {% data variables.product.prodname_code_scanning %} 警报。
 
 {% note %}
 
-**Note:**
-{% ifversion fpt or ghec %}
-* The {% data variables.code-scanning.codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+注意：{% ifversion fpt or ghec %}
+* {% data variables.code-scanning.codeql_runner %} 使用 {% data variables.product.prodname_codeql %} CLI 来分析代码，因此具有相同的许可条件。 它可自由用于 {% data variables.product.prodname_dotcom_the_website %} 上维护的公共仓库，并且可用于具有 {% data variables.product.prodname_advanced_security %} 许可证的客户所拥有的私有仓库。 有关信息，请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”以及“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
 {% else %}
-* The {% data variables.code-scanning.codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
-{% endif %}
-{% ifversion ghae %}
-* The {% data variables.code-scanning.codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries.
-For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
-{% endif %}
-{% endnote %}
+* {% data variables.code-scanning.codeql_runner %} 可供拥有 {% data variables.product.prodname_advanced_security %} 许可证的客户使用。
+{% endif %} {% ifversion ghae %}
+* 请勿将 {% data variables.code-scanning.codeql_runner %} 与 {% data variables.product.prodname_codeql %} CLI 混淆。 {% data variables.product.prodname_codeql %} CLI 是一个命令行接口，允许您创建用于安全研究的 {% data variables.product.prodname_codeql %} 数据库并运行 {% data variables.product.prodname_codeql %} 查询。
+有关详细信息，请参阅“[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)”。
+{% endif %} {% endnote %}
 
-## Downloading the {% data variables.code-scanning.codeql_runner %}
+## 下载 {% data variables.code-scanning.codeql_runner %}
 
-You can download the {% data variables.code-scanning.codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+可以从 https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases 下载 {% data variables.code-scanning.codeql_runner %}。 在某些操作系统上，您可能需要更改下载文件的权限才能运行它。
 
-On Linux:
+在 Linux 上：
 
 ```shell
 chmod +x codeql-runner-linux
 ```
 
-On macOS:
+在 macOS 上：
 
 ```shell
 chmod +x codeql-runner-macos
 sudo xattr -d com.apple.quarantine codeql-runner-macos
 ```
 
-On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
+在 Windows 中，`codeql-runner-win.exe` 文件通常无需更改权限。
 
-## Adding the {% data variables.code-scanning.codeql_runner %} to your CI system
+## 将 {% data variables.code-scanning.codeql_runner %} 添加到 CI 系统
 
-Once you download the {% data variables.code-scanning.codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example: 
+下载 {% data variables.code-scanning.codeql_runner %} 并确认它可执行后，应将该运行器提供给打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 例如，您可以配置每台服务器从中央内部位置复制运行器。 或者，您也可以使用 REST API 直接从 {% data variables.product.prodname_dotcom %} 获取运行器，例如： 
 
 ```shell
 wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
-In addition to this, each CI server also needs:
+除此之外，每个 CI 服务器还需要：
 
-- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.code-scanning.codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
-- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.code-scanning.codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+- 供 {% data variables.code-scanning.codeql_runner %} 使用的 {% data variables.product.prodname_github_app %} 或 {% data variables.product.pat_generic %}。 必须使用具有 `repo` 范围的访问令牌，或具有 `security_events` 写入权限和 `metadata` 与 `contents` 读取权限的 {% data variables.product.prodname_github_app %}。 有关信息，请参阅“[生成 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建 {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)”。
+- 访问与此版本的 {% data variables.code-scanning.codeql_runner %} 关联的 {% data variables.product.prodname_codeql %} 捆绑包。 此包包含 {% data variables.product.prodname_codeql %} 分析所需的查询和库，以及供运行器内部使用的 {% data variables.product.prodname_codeql %} CLI。 有关信息，请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
 
-The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+提供 {% data variables.product.prodname_codeql %} 包访问权限的选项：
 
-1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.code-scanning.codeql_runner %} can download the bundle automatically.
-1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.code-scanning.codeql_runner %}.
+1. 允许 CI 服务器访问 https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action，以便 {% data variables.code-scanning.codeql_runner %} 可以自动下载捆绑包。
+1. 手动下载/解压缩捆绑包，将其与其他中心资源一起存储，并使用 <nobr>`--codeql-path`</nobr> 标志在调用中指定捆绑包的位置以初始化 {% data variables.code-scanning.codeql_runner %}。
 
-## Calling the {% data variables.code-scanning.codeql_runner %}
+## 调用 {% data variables.code-scanning.codeql_runner %}
 
-You should call the {% data variables.code-scanning.codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+你应该从要分析的存储库的签出位置调用 {% data variables.code-scanning.codeql_runner %}。 两个主要命令是：
 
-1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
-1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
+1. `init` 需要初始化运行器并为需要分析的每种语言创建一个 {% data variables.product.prodname_codeql %} 数据库。 这些数据库由后续命令填充和分析。
+1. `analyze` 需要填充 {% data variables.product.prodname_codeql %} 数据库、分析它们并将结果上传到 {% data variables.product.product_name %}。
 
-For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or {% data variables.product.pat_generic %} to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
+对于这两个命令，都必须指定 {% data variables.product.product_name %} 的 URL、存储库 OWNER/NAME 以及 {% data variables.product.prodname_github_apps %} 或用于身份验证的 {% data variables.product.pat_generic %}。 还需要指定 CodeQL 包的位置，除非 CI 服务器有权直接从 `github/codeql-action` 存储库下载它。
 
-You can configure where the {% data variables.code-scanning.codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
+可以配置 {% data variables.code-scanning.codeql_runner %} 存储 CodeQL 捆绑包的位置，以便将来使用 <nobr>`--tools-dir`</nobr> 标志在服务器上进行分析，还可配置在使用 <nobr>`--temp-dir`</nobr> 进行分析的过程中储存临时文件的位置。
 
-To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
+要查看运行器的命令行引用，请使用 `-h` 标志。 例如，要列出所有命令，请运行：`codeql-runner-OS -h`，或者要列出可用于 `init` 命令的所有标志，请运行：`codeql-runner-OS init -h`（其中 `OS` 因你使用的可执行文件而异）。 有关详细信息，请参阅“[在 CI 系统中配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)”。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### Basic example
+### 基本示例
 
-This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
+此示例在 Linux CI 服务器上为托管在 `{% data variables.command_line.git_url_example %}` 上的 `octo-org/example-repo` 存储库运行 {% data variables.product.prodname_codeql %} 分析。 这个过程非常简单，因为仓库只包含可通过 {% data variables.product.prodname_codeql %} 直接分析的语言，而无需构建（例如 Go、JavaScript、Python 和 TypeScript）。
 
-In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
+在此示例中，服务器有权直接从 `github/codeql-action` 存储库下载 {% data variables.product.prodname_codeql %} 包，因此无需使用 `--codeql-path` 标志。
 
-1. Check out the repository to analyze.
-1. Move into the directory where the repository is checked out.
-1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+1. 检出要分析的仓库。
+1. 移至检出仓库的目录。
+1. 初始化 {% data variables.code-scanning.codeql_runner %} 并为检测到的语言创建 {% data variables.product.prodname_codeql %}。
 
     ```shell
     $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
@@ -131,13 +131,13 @@ In this example, the server has access to download the {% data variables.product
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
-### Compiled language example
+### 编译语言示例
 
-This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
+此示例与前面的示例相似，但此例中的仓库含有用 C/C++、C# 或 Java 编写的代码。 要为这些语言创建 {% data variables.product.prodname_codeql %} 数据库，CLI 需要监控构建。 在初始化过程结束时，运行器会报告您需要在构建代码之前设置环境的命令。 你需要在调用正常的 CI 构建进程之前运行此命令，然后运行 `analyze` 命令。
 
-1. Check out the repository to analyze.
-1. Move into the directory where the repository is checked out.
-1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+1. 检出要分析的仓库。
+1. 移至检出仓库的目录。
+1. 初始化 {% data variables.code-scanning.codeql_runner %} 并为检测到的语言创建 {% data variables.product.prodname_codeql %}。
     ```shell
     $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
         --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
@@ -148,37 +148,37 @@ This example is similar to the previous example, however this time the repositor
       Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
       ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
     ```
-1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
+1. 获取由 `init` 操作生成的脚本以设置环境，从而监视生成。 请注意以下代码片段中的先导点和空间。
 
     ```shell
     $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
     ```
 
-1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)."
+1. 构建代码。 在 macOS 上，需要使用环境变量 `$CODEQL_RUNNER` 为构建命令添加前缀。 有关详细信息，请参阅“[对 CI 系统中的 {% data variables.code-scanning.codeql_runner %} 进行故障排除](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)”。
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
 {% note %}
 
-**Note:** If you use a containerized build, you need to run the {% data variables.code-scanning.codeql_runner %} in the container where your build task takes place.
+注意：如果使用容器化生成，则需要在执行生成任务的容器中运行 {% data variables.code-scanning.codeql_runner %}。
 
 {% endnote %}
 
-## Further reading
+## 延伸阅读
 
-- "[Configuring {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
-- "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
+- [在 CI 系统中配置 {% data variables.code-scanning.codeql_runner %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)
+- [对 CI 系统中的 {% data variables.code-scanning.codeql_runner %} 进行故障排除](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)
 
 {% else %}
 
-## About the {% data variables.code-scanning.codeql_runner %}
+## 关于 {% data variables.code-scanning.codeql_runner %}
 
-The {% data variables.code-scanning.codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity.
+{% data variables.code-scanning.codeql_runner %} 已被弃用。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) 版本 2.7.6 具有完整的功能奇偶一致性。
 
-For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
+有关迁移到 {% data variables.product.prodname_codeql_cli %} 的信息，请参阅“[从 CodeQL 运行器迁移到 CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)”。
 
-## Further reading
+## 延伸阅读
 
-- [CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) in the GitHub Blog
+- GitHub 博客中的 [CodeQL 运行器弃用](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/)
 
 {% endif %}

translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md

@@ -463,7 +463,13 @@ jobs:
 
 ### Enable auto-merge on a pull request
 
-If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when any tests and approvals required by the branch protection rules are successfully met. For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+{% note %}
+
+**Note:** If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless all the required status checks pass. For more information, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+{% endnote %}
 
 You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`:
 

translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md

@@ -0,0 +1,44 @@
+---
+title: Configuring private vulnerability reporting for a repository
+intro: Owners and administrators of public repositories can allow security researchers to report vulnerabilities securely in the repository by enabling private vulnerability reporting.
+permissions: 'Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+miniTocMaxHeadingLevel: 3
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Configure private vulnerability reporting
+---
+
+{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
+
+## About privately reporting a security vulnerability
+
+Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+
+{% data reusables.security-advisory.private-vulnerability-reporting-overview %}
+
+For maintainers, the benefits of using private vulnerability reporting are: 
+- Less risk of being contacted publicly, or via undesired means.
+- Receive reports in the same platform you resolve them in for simplicity
+- The security researcher creates or at least initiates the advisory report on the behalf of maintainers.
+- Maintainers receive reports in the same platform as the one used to discuss and resolve the advisories.
+- Vulnerability less likely to be in the public eye.
+- The opportunity to discuss vulnerability details privately with security researchers and collaborate on the patch.
+
+## Enabling or disabling private vulnerability reporting for a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
+
+ ![Screenshot of the "Code security and analysis" page with the "Enable" button emphasized for private vulnerability reporting](/assets/images/help/security/private-vulnerability-reporting-enable-or-disable.png)
+
+When a maintainer enables private security reporting for their repository, security researchers will see a new button in the **Advisories** page of the repository. The security researcher can click this button to privately report a security vulnerability to the repository maintainer. 
+
+ ![Screenshot showing the "Report a vulnerability" button](/assets/images/help/security/report-a-vulnerability-button.png)
+   

translations/zh-CN/content/codespaces/overview.md

@@ -1,7 +1,7 @@
 ---
-title: GitHub Codespaces overview
+title: GitHub Codespaces 概述
 shortTitle: Overview
-intro: 'This guide introduces {% data variables.product.prodname_github_codespaces %} and provides details on how it works and how to use it.'
+intro: '本指南介绍了 {% data variables.product.prodname_github_codespaces %}，并详细介绍了它的工作原理和使用方法。'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /codespaces/codespaces-reference/about-codespaces
@@ -15,52 +15,57 @@ versions:
 type: overview
 topics:
   - Codespaces
+ms.openlocfilehash: a1618c86671bc5b06474c41803c6b34576a897aa
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160798'
 ---
+## 什么是代码空间？
 
-## What is a codespace?
+代码空间是托管在云中的开发环境。 可通过将[配置文件](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)提交到存储库（通常称为“配置即代码”）来为 {% data variables.product.prodname_github_codespaces %} 自定义项目，这将为项目的所有用户创建可重复的 codespace 配置。
 
-A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project.
+每个 codespace 都在由 {% data variables.product.prodname_dotcom %} 托管的虚拟机上运行。 可以根据需要的资源选择要使用的计算机类型。 有各种类型的计算机可供选择，从 2 核处理器、4 GB RAM 和 32 GB 存储开始。 
 
-Each codespace runs on a virtual machine hosted by {% data variables.product.prodname_dotcom %}. You can choose the type of machine you want to use, depending on the resources you need. Various types of machine are available, starting with a 2-core processor, 4 GB of RAM, and 32 GB of storage. 
+可以从浏览器、{% data variables.product.prodname_vscode %}、JetBrains Gateway 应用程序或使用 {% data variables.product.prodname_cli %} 连接到 codespaces。
 
-You can connect to your codespaces from your browser, from {% data variables.product.prodname_vscode %}, from the JetBrains Gateway application, or by using {% data variables.product.prodname_cli %}.
+![显示 {% data variables.product.prodname_github_codespaces %} 工作原理的示意图](/assets/images/help/codespaces/codespaces-diagram.png)
 
-![A diagram showing how {% data variables.product.prodname_github_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png)
+## 使用 {% data variables.product.prodname_github_codespaces %}
 
-## Using {% data variables.product.prodname_github_codespaces %}
-
-To begin developing using cloud-based compute resources, you can create a codespace from a template or from any branch or commit in a repository. When you create a codespace from a template, you can start from a blank template or choose a template suitable for the work you're doing.
+要开始使用基于云的计算资源进行开发，可以通过模板或存储库中的任何分支或提交创建 codespace。 通过模板创建 codespace 时，可以从空白模板开始，也可以选择适合你正在做的工作的模板。
 
 {% data reusables.codespaces.links-to-get-started %}
 
-### Using codespaces owned by your personal account
+### 使用个人帐户拥有的 codespaces
 
-All personal {% data variables.product.prodname_dotcom_the_website %} accounts have a monthly quota of free use of {% data variables.product.prodname_github_codespaces %} included in the Free or Pro plan. You can get started using {% data variables.product.prodname_github_codespaces %} on your personal account without changing any settings or providing payment details.
+所有个人 {% data variables.product.prodname_dotcom_the_website %} 帐户都有免费或专业版计划中包含的 {% data variables.product.prodname_github_codespaces %} 的每月免费使用配额。 无需更改任何设置或提供付款详细信息，即可在个人帐户上开始使用 {% data variables.product.prodname_github_codespaces %}。
 
-You can create and use a codespace for any repository you can clone. You can also use a template to create codespaces that are not initially associated with a repository. If you create a codespace from an organization-owned repository, use of the codespace will either be charged to the organization (if the organization is configured for this), or to your personal account. Codespaces created from templates are always charged to your personal account. 
+可为可以克隆的任何存储库创建和使用 codespace。 还可以使用模板来创建最初不与存储库关联的 codespaces。 如果通过组织拥有的存储库创建 codespace，则 codespace 的使用按照组织（如果组织对此进行了配置）或个人帐户进行计费。 通过模板创建的 codespaces 始终按照个人帐户进行计费。 
 
 {% data reusables.codespaces.codespaces-continue-by-paying %} 
 
-### Using organization-owned codespaces
+### 使用组织拥有的 codespaces
 
-Organization owners can enable use of {% data variables.product.prodname_github_codespaces %}, billable to the organization or enterprise account. This applies to codespaces created from repositories owned by the organization. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." You can set a spending limit for use of {% data variables.product.prodname_github_codespaces %} on your organization or enterprise account. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
+组织所有者可以启用 {% data variables.product.prodname_github_codespaces %}，后者可按照组织或企业帐户计费。 这适用于通过组织拥有的存储库创建的 codespaces。 有关详细信息，请参阅“[为组织启用 {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)”。 可以对组织或企业帐户上的 {% data variables.product.prodname_github_codespaces %} 使用设置支出限制。 有关详细信息，请参阅“[管理 {% data variables.product.prodname_github_codespaces %} 的支出限制](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)”。
 
-If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." Codespaces that are billed to an organization, or its parent enterprise, are owned by the organization and can be deleted an organization owner. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)." 
+如果按照组织或企业对 codespace 的使用进行计费，则会在创建 codespace 时显示。 有关详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)”。 按照组织或其父企业计费的 codespaces 归组织所有，且可被组织所有者删除。 有关详细信息，请参阅“[删除 codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)”。 
 
-### Customizing {% data variables.product.prodname_github_codespaces %}
+### 自定义 {% data variables.product.prodname_github_codespaces %}
 
-To customize the runtimes and tools in your codespace, you can create one or more dev container configurations for your repository. Adding dev container configurations to your repository allows you to define a choice of different development environments that are appropriate for the work people will do in your repository. 
+若要自定义 codespace 中的运行时和工具，可以为存储库创建一个或多个开发容器配置。 将开发容器配置添加到存储库后，可以定义适合用户将在存储库中执行的工作的不同开发环境选择。 
 
-If you create a codespace from a repository without any dev container configurations, {% data variables.product.prodname_github_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. If you create a codespace from a template, you might start with some initial configuration on top of the default image. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+如果通过没有任何开发容器配置的存储库创建 codespace，{% data variables.product.prodname_github_codespaces %} 会将存储库克隆到具有默认 codespace 映像的环境中，该映像包含许多工具、语言和运行时环境。 如果通过模板创建 codespace，则可以从默认映像之上的一些初始配置开始。 有关详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
 
-You can personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository. You can use dotfiles to set shell aliases and preferences, or to install your personal preference of the tools you like to use. If you use {% data variables.product.prodname_github_codespaces %} in the browser, or in {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to give your codespace editor the same settings, keyboard shortcuts, snippets, and extensions that you have set up in your local installation of {% data variables.product.prodname_vscode %}. 
+可使用公共[点文件](https://dotfiles.github.io/tutorials/)存储库对 codespace 环境的各个方面进行个性化设置。 可使用点文件设置 shell 别名和首选项，也可安装喜欢使用的工具的个人首选项。 如果在浏览器或 {% data variables.product.prodname_vscode %} 中使用 {% data variables.product.prodname_github_codespaces %}，则可以使用[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)为 codespace 编辑器提供在本地安装 {% data variables.product.prodname_vscode %} 中设置的相同设置、键盘快捷方式、片段和扩展。 
 
-For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
+有关详细信息，请参阅“[自定义代码空间](/codespaces/customizing-your-codespace)”。
 
-## Billing for {% data variables.product.prodname_codespaces %}
+## {% data variables.product.prodname_codespaces %} 的计费
 
-For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+有关 {% data variables.product.prodname_github_codespaces %} 的定价、存储和使用情况的信息，请参阅“[有关 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)”。
 
 {% data reusables.codespaces.codespaces-spending-limit-requirement %} 
 
-{% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
+{% data reusables.codespaces.codespaces-monthly-billing %} 有关组织所有者和计费管理员如何管理组织的 {% data variables.product.prodname_github_codespaces %} 的支出限制的信息，请参阅“[管理 {% data variables.product.prodname_github_codespaces %} 的支出限制](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)”。

translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md

@@ -1,6 +1,6 @@
 ---
-title: The github.dev web-based editor
-intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.'
+title: github.dev 基于 web 的编辑器
+intro: '使用存储库或拉取请求中的 github.dev {% data variables.product.prodname_serverless %} 来创建和提交更改。'
 versions:
   feature: githubdev-editor
 type: how_to
@@ -12,104 +12,108 @@ topics:
 shortTitle: Web-based editor
 redirect_from:
   - /codespaces/developing-in-codespaces/web-based-editor
+ms.openlocfilehash: d1c21f3e75ecc4fec282c9156943c137287d203c
+ms.sourcegitcommit: caab4edbbeedf23e9062e48a67c35224772b6efa
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160475'
 ---
-
 {% note %}
 
-**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/general).
+注意：github.dev {% data variables.product.prodname_serverless %} 目前为测试预览版。 你可以在[我们的讨论中](https://github.com/community/community/discussions/categories/general)提供反馈。
 
 {% endnote %}
 
-## About the {% data variables.product.prodname_serverless %}
+## 关于 {% data variables.product.prodname_serverless %}
 
-The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor.
+{% data variables.product.prodname_serverless %} 引入了完全在浏览器中运行的轻量级编辑体验。 使用 {% data variables.product.prodname_serverless %}，您可以从 {% data variables.product.prodname_dotcom %}中导航文件和源代码存储库，并创建和提交代码更改。 您可以在编辑器中打开任何存储库、复刻或拉取请求。
 
-The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}.
+{% data variables.product.prodname_serverless %} 在 {% data variables.product.prodname_dotcom_the_website %} 上免费供所有人使用。
 
-The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+{% data variables.product.prodname_serverless %} 具有 {% data variables.product.prodname_vscode %} 的诸多优点，如搜索、语法突出显示和源控制视图。 还可以使用 Settings Sync 与编辑器共享自己的 {% data variables.product.prodname_vscode_shortname %} 设置。 有关详细信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)”。
 
-The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
+{% data variables.product.prodname_serverless %} 完全在浏览器的沙盒中运行。 编辑器不会克隆存储库，而是使用 [GitHub 存储库扩展](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)来执行你将要使用的大部分功能。 您的工作将保存在浏览器的本地存储中，直到您提交为止。 您应定期提交更改，以确保它们始终可访问。
 
-You must be signed in to use the web-based editor.
+必须登录才能使用基于 Web 的编辑器。
 
-## Opening the {% data variables.product.prodname_serverless %}
+## 打开 {% data variables.product.prodname_serverless %}
 
-You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
+您可以通过以下任一方式打开 {% data variables.product.prodname_serverless %} 中的任何 {% data variables.product.prodname_dotcom %} 存储库：
 
-- To open the repository in the same browser tab, press <kbd>.</kbd> while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
+- 要在同一浏览器标签页中打开存储库，请按 <kbd>.</kbd> （在 {% data variables.product.prodname_dotcom %} 上浏览任何存储库或拉取请求时）。
  
-  To open the repository in a new browser tab, press <kbd>></kbd>.
+  要在新的浏览器标签页中打开存储库，请按 <kbd>></kbd>。
 
-- Change the URL from "github.com" to "github.dev".
-- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
+- 将 URL 从“github.com”更改为“github.dev”。
+- 查看文件时，请使用 {% octicon "pencil" aria-label="The edit icon" %} 旁边的下拉菜单，然后选择“在 github.dev 中打开”。
 
-  ![Edit file button dropdown menu](/assets/images/help/repository/edit-file-edit-dropdown.png)
+  ![“编辑文件”按钮下拉菜单](/assets/images/help/repository/edit-file-edit-dropdown.png)
 
-## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %}
+## {% data variables.product.prodname_codespaces %} 和 {% data variables.product.prodname_serverless %}
 
-Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_github_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case.
+{% data variables.product.prodname_serverless %} 和 {% data variables.product.prodname_github_codespaces %} 都允许你直接从存储库中编辑代码。 但两者的优点略有不同，具体取决于您的使用情况。
 
 || {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_github_codespaces %}|
 |-|----------------|---------|
-| **Cost** | Free.      | Free monthly quota of usage for personal accounts. For information on pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)."|
-| **Availability** | Available to everyone on GitHub.com. | Available to everyone on GitHub.com. |
-| **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." |
-| **Compute**  | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With  {%  data variables.product.prodname_github_codespaces %}, you get the power of a dedicated VM on which you can run and debug your application.|
-| **Terminal access** | None. | {% data variables.product.prodname_github_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.|
-| **Extensions**  | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With {% data variables.product.prodname_github_codespaces %}, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.|
+| **成本** | 可用。      | 个人帐户每月免费使用配额。 有关定价的信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#github-codespaces-pricing)”。|
+| **可用性** | 可供 GitHub.com 上的所有人使用。 | 可供 GitHub.com 上的所有人使用。 |
+| **启动** | {% data variables.product.prodname_serverless %} 在按下按键时可立即打开，您可以立即开始使用它，而无需等待其他配置或安装。 | 创建或恢复 codespace 时，将为该 codespace 分配一个 VM，并根据 `devcontainer.json` 文件的内容配置容器。 此设置可能需要几分钟才能创建环境。 有关详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)”。 |
+| **计算**  | 没有关联的计算，因此您将无法创建和运行代码或使用集成终端。 | 借助 {%  data variables.product.prodname_github_codespaces %}，可以获得专用 VM 的强大功能，在该 VM 上可以运行和调试应用程序。|
+| **终端访问** | 无。 | 默认情况下，{% data variables.product.prodname_github_codespaces %} 提供一组通用工具，这意味着可以像在本地环境中一样使用终端。|
+| **扩展**  | 只有可以在 Web 中运行的扩展子集才会显示在扩展视图中，并且可以安装。 有关详细信息，请参阅[使用扩展](#using-extensions)。| 借助 {% data variables.product.prodname_github_codespaces %}，可以使用 {% data variables.product.prodname_vscode_marketplace %} 中的大多数扩展。|
 
-### Continue working on {% data variables.product.prodname_codespaces %}
+### 继续使用 {% data variables.product.prodname_codespaces %}
 
-You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace. If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}.
+你可以在 {% data variables.product.prodname_serverless %} 中启动工作流并继续使用 codespace。 如果尝试访问运行和调试视图或终端，系统将通知您它们在 {% data variables.product.prodname_serverless %} 中不可用。
 
-To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes.
+要在 codespace 中继续工作，请单击“继续处理...” 然后选择“新建 Codespace”，在当前分支上创建 codespace。 在选择此选项之前，必须提交任何更改。
 
-![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png)
+![显示 UI 中的“继续工作”按钮的屏幕截图](/assets/images/help/codespaces/codespaces-continue-working.png)
 
-## Using source control
+## 使用源控制
 
-When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+使用 {% data variables.product.prodname_serverless %} 时，所有操作都通过源控制视图进行管理，该视图位于左侧的活动栏中。 有关源代码管理视图的详细信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[版本控制](https://code.visualstudio.com/docs/editor/versioncontrol)”。
 
-Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+由于基于 Web 的编辑器使用 GitHub 存储库扩展来增强其功能，因此您可以切换分支而无需隐藏更改。 有关详细信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[GitHub 存储库](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)”。
 
-### Create a new branch
+### 创建新分支
 
-{% data reusables.codespaces.create-or-switch-branch %}
-  Any uncommitted changes you have made in your old branch will be available on your new branch.
+{% data reusables.codespaces.create-or-switch-branch %} 你在旧分支中所做的任何未提交的更改都将在新分支上可用。
 
-### Commit your changes
+### 提交更改
 
 {% data reusables.codespaces.source-control-commit-changes %} 
-5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}.
-### Create a pull request
+5. 更改在提交后将自动推送到 {% data variables.product.prodname_dotcom %} 上的分支。
+### 创建拉取请求
 
 {% data reusables.codespaces.source-control-pull-request %}
 
-### Working with an existing pull request
+### 使用现有的拉取请求
 
-You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request.
+您可以使用 {% data variables.product.prodname_serverless %} 来处理现有的拉取请求。
 
-1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}.
-2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}.
-3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes.
+1. 浏览到要在 {% data variables.product.prodname_serverless %} 中打开的拉取请求。
+2. 按 `.` 以在 {% data variables.product.prodname_serverless %} 中打开拉取请求。
+3. 进行任何更改后，请使用[提交更改](#commit-your-changes)中的步骤提交更改。 您的更改将直接提交到分支，无需推送更改。
 
-## Using extensions
+## 使用扩展
 
-The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+{% data variables.product.prodname_serverless %} 支持专门创建或更新以在 Web 中运行的 {% data variables.product.prodname_vscode_shortname %} 扩展。 这些扩展称为“Web 扩展”。 要了解如何创建 Web 扩展或更新现有扩展以适用于 Web，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[Web 扩展](https://code.visualstudio.com/api/extension-guides/web-extensions)”。
 
-Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+可以在 {% data variables.product.prodname_serverless %} 中运行的扩展将显示在扩展视图中，并且可以安装。 如果使用“设置同步”，则所有兼容的扩展也会自动安装。 有关信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)”。
 
 
-## Troubleshooting
+## 故障排除
 
-If you have issues opening the {% data variables.product.prodname_serverless %}, try the following:
+如果您在打开 {% data variables.product.prodname_serverless %} 时遇到问题，请尝试以下操作：
 
-- Make sure you are signed in to {% data variables.product.prodname_dotcom %}.
-- Disable any ad blockers.
-- Use a non-incognito window in your browser to open the {% data variables.product.prodname_serverless %}.
+- 确保您已登录到 {% data variables.product.prodname_dotcom %}。
+- 禁用任何广告拦截器。
+- 在浏览器中使用非隐身窗口打开 {% data variables.product.prodname_serverless %}。
 
-### Known limitations
+### 已知的限制
 
-- The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
-- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation.
-- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
+- {% data variables.product.prodname_serverless %} 目前在 Chrome（以及其他各种基于 Chromium 的浏览器）、Edge、Firefox 和 Safari 中受支持。 我们建议您使用这些浏览器的最新版本。
+- 某些按键绑定可能不起作用，具体取决于您使用的浏览器。 这些键绑定限制记录在 {% data variables.product.prodname_vscode_shortname %} 文档的“[已知限制和改编](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)”部分中。
+- 根据本地键盘布局，`.` 可能无法打开 {% data variables.product.prodname_serverless %}。 在这种情况下，你可以通过将 URL 从 `github.com` 更改为 `github.dev` 来打开 {% data variables.product.prodname_serverless %} 中的任何 {% data variables.product.prodname_dotcom %} 存储库。

translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md

@@ -1,6 +1,6 @@
 ---
-title: 阻止用户访问组织
-intro: 组织所有者和版主可以阻止非组织成员的任何人在组织的存储库上进行协作。
+title: Blocking a user from your organization
+intro: Organization owners and moderators can block anyone who is not a member of the organization from collaborating on the organization's repositories.
 redirect_from:
   - /articles/blocking-a-user-from-your-organization
   - /github/building-a-strong-community/blocking-a-user-from-your-organization
@@ -10,71 +10,68 @@ versions:
 topics:
   - Community
 shortTitle: Block from your org
-ms.openlocfilehash: 3264bb71f157c2ec34f42b859857eed4253379f3
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145086591'
 ---
-可以从组织的设置中或从用户发表的特定评论中阻止非成员用户。 在评论中阻止用户时，您可以选择向该用户发送通知，以告知他们已被阻止并说明原因。 否则，用户不会直接收到您已阻止他们的通知。 被阻止的用户仍然可以删除其现有内容。
 
-阻止用户时，您可以选择无限期或在特定时间段内阻止他们。 如果在特定时间段内阻止某人，则所选时间结束后会自动解除对他们的阻止。 如果无限期阻止某人，您可以随时手动解除阻止。 有关详细信息，请参阅“[取消阻止用户对组织的访问](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)”。
+You can block non-members from within your organization's settings or from a specific comment made by a user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
+
+{% data reusables.organizations.blocking-a-user %}
 
 {% tip %}
 
-**提示：** 如果你因为言辞激烈的对话而阻止用户，请考虑锁定对话，以限制为只有协作者才能评论。 有关详细信息，请参阅“[锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)”。
+**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
 
 {% endtip %}
 
-阻止用户访问组织时：
-- 该用户停止关注您组织的仓库。
-- 该用户的星标和议题分配从您的仓库中删除
-- 该用户对您组织仓库中的讨论或评论的投票将被删除
-- 该用户在您组织仓库中的协作者身份被删除
-- 该用户对您组织的仓库的贡献不再计为他们的贡献
-- 任何对被阻止用户的待处理仓库或组织邀请都被取消
+At the time that you block a user from your organization:
+- The user stops watching your organization's repositories
+- The user's stars and issue assignments are removed from your repositories
+- The user's votes on discussions or comments in your organization's repositories are deleted
+- The user is removed as a collaborator on your organization's repositories
+- The user's contributions to your organization's repositories are no longer counted as contributions for them
+- Any pending repository or organization invitations to the blocked user are cancelled
 
-阻止用户访问组织后，他们无法：
-- 在评论中交叉引用您组织的仓库
-- 复刻、关注、固定您组织的仓库或对其标星
+After you've blocked a user from your organization, they cannot:
+- Cross-reference your organization's repositories in comments
+- Fork, watch, pin, or star your organization's repositories
 
-在您组织的仓库中，被阻止的用户也不能：
-- 打开议题
-- 发送、关闭或合并拉取请求
-- 对议题、拉取请求或提交发表评论
-- 添加或编辑 wiki 页面
+In your organization's repositories, blocked users also cannot:
+- Open issues
+- Send, close, or merge pull requests
+- Comment on issues, pull requests, or commits
+- Add or edit wiki pages
 
-## 在评论中阻止用户
+## Blocking a user in a comment
 
-1. 导航到您要阻止其作者的评论。
-2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击“阻止用户”。
-![显示阻止用户选项的水平烤肉串图标和评论审核菜单](/assets/images/help/repository/comment-menu-block-user.png)
-3. 如果要设置阻止的时限，请使用 Block user（阻止用户）下拉菜单，选择要阻止该用户的时间段。
-![阻止用户下拉菜单中的阻止时限](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
-4. 如果要隐藏该用户在组织中发表的所有评论，请选择“隐藏此用户的评论”并选择原因。
-![在阻止用户下拉菜单中发送通知](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
-5. 如果要将阻止的原因告知用户，请选择“向此用户发送通知”。
-![在阻止用户下拉菜单中发送通知](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
-6. 若要阻止用户，请单击“阻止用户访问组织”或“阻止用户访问组织并发送消息” 。
-![阻止用户按钮](/assets/images/help/organizations/org-block-user-button-in-comment.png)
+1. Navigate to the comment whose author you would like to block.
+2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block user**.
+![The horizontal kebab icon and comment moderation menu showing the block user option](/assets/images/help/repository/comment-menu-block-user.png)
+3. If you'd like to set a time limit for the block, use the Block user drop-down menu, and select the amount of time you'd like to block the user.
+![Block time limit in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
+4. If you'd like to hide all of the comments the user has made in the organization, select **Hide this user's comments** and choose a reason.
+![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
+5. If you'd like to notify the user why they're being blocked, select **Send a notification to this user**.
+![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
+6. To block the user, click **Block user from organization** or **Block user from organization and send message**.
+![Block user button](/assets/images/help/organizations/org-block-user-button-in-comment.png)
 
-## 在组织设置中阻止用户
+## Blocking a user in the organization settings
 
-1. 若要阻止组织成员，请首先从组织中[删除用户](/articles/removing-a-member-from-your-organization)。
+1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
 
-{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.block_users %}
-6. 在“Block a user（阻止用户）”下，键入要阻止的用户的用户名。
-![用户名字段](/assets/images/help/organizations/org-block-username-field.png)
-7. 如果要设置阻止的时限，请使用 Block options（阻止选项）下拉菜单，选择要阻止该用户的时间段。
-![阻止选项下拉菜单](/assets/images/help/organizations/org-block-options-menu.png)
-8. 单击“阻止用户”。
-![阻止按钮](/assets/images/help/organizations/org-block-user-button.png)
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.block_users %}
+6. Under "Block a user", type the username of the user you'd like to block.
+![Username field](/assets/images/help/organizations/org-block-username-field.png)
+7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user.
+![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png)
+8. Click **Block user**.
+![Block button](/assets/images/help/organizations/org-block-user-button.png)
 
-## 延伸阅读
+## Further reading
 
-- “[查看被阻止访问组织的用户](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)”
-- “[取消阻止用户对组织的访问](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)”
-- “[阻止用户访问你的个人帐户](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)”
-- “[取消阻止用户对个人帐户的访问](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)”
-- “[举报滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)”
+- "[Viewing users who are blocked from your organization](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)"
+- "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
+- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
+- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
+- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"

translations/zh-CN/content/copilot/overview-of-github-copilot/about-github-copilot.md

@@ -1,41 +1,46 @@
 ---
-title: About GitHub Copilot
-intro: '{% data variables.product.prodname_copilot %} can help you code by offering autocomplete-style suggestions. You can learn what to consider while using {% data variables.product.prodname_copilot %}, and how {% data variables.product.prodname_copilot %} works.'
+title: 关于 GitHub Copilot
+intro: '{% data variables.product.prodname_copilot %} 可以通过提供自动完成样式的建议来帮助你编写代码。 可以了解使用 {% data variables.product.prodname_copilot %} 时要考虑的事项，以及 {% data variables.product.prodname_copilot %} 的工作原理。'
 versions:
   feature: copilot
 topics:
   - Copilot
 shortTitle: About GitHub Copilot
+ms.openlocfilehash: dd4538cb4cf6fc9dd84bb3f0d05bf8a85559d5ec
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160638'
 ---
+## 关于 {% data variables.product.prodname_copilot %}
 
-## About {% data variables.product.prodname_copilot %}
+{% data variables.product.prodname_copilot %} 是一个 AI 配对程序员，可在编写代码时提供自动完成样式的建议。 可以从 {% data variables.product.prodname_copilot %} 接收建议，方法是开始编写要使用的代码，或者编写描述代码要执行的操作的自然语言注释。 {% data variables.product.prodname_copilot %} 会分析你正在编辑的文件以及相关文件中的上下文，并在文本编辑器中提供建议。 {% data variables.product.prodname_copilot %} 由 OpenAI Codex 提供支持，OpenAI Codex 是一个由 OpenAI 创建的新 AI 系统。
 
-{% data variables.product.prodname_copilot %} is an AI pair programmer that offers autocomplete-style suggestions as you code. You can receive suggestions from {% data variables.product.prodname_copilot %} either by starting to write the code you want to use, or by writing a natural language comment describing what you want the code to do. {% data variables.product.prodname_copilot %} analyzes the context in the file you are editing, as well as related files, and offers suggestions from within your text editor. {% data variables.product.prodname_copilot %} is powered by OpenAI Codex, a new AI system created by OpenAI.
+针对公共存储库中出现的所有语言对 {% data variables.product.prodname_copilot %} 进行了培训。 对于每种语言，收到的建议质量可能取决于该语言训练数据的数量和多样性。 例如，JavaScript 在公共存储库中表现良好，并且是 {% data variables.product.prodname_copilot %} 最受支持的语言之一。 在公共存储库中具有较少代表性的语言可能会产生较少或较不可靠的建议。
 
-{% data variables.product.prodname_copilot %} is trained on all languages that appear in public repositories. For each language, the quality of suggestions you receive may depend on the volume and diversity of training data for that language. For example, JavaScript is well-represented in public repositories and is one of {% data variables.product.prodname_copilot %}'s best supported languages. Languages with less representation in public repositories may produce fewer or less robust suggestions.
+{% data variables.product.prodname_copilot %} 在 Visual Studio Code、Visual Studio、Neovim 和 IDE 的 JetBrains 套件中作为扩展提供。 有关详细信息，请参阅“[{% data variables.product.prodname_copilot %} 入门指南](/copilot/getting-started-with-github-copilot)”。
 
-{% data variables.product.prodname_copilot %} is available as an extension in Visual Studio Code, Visual Studio, Neovim and the JetBrains suite of IDEs. For more information, see "[Getting started with {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot)."
+## 使用 {% data variables.product.prodname_copilot %}
 
-## Using {% data variables.product.prodname_copilot %}
+可以看到 {% data variables.product.prodname_copilot %} 的实际示例。 有关详细信息，请参阅 [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) 网站。 
 
-You can see real-world examples of {% data variables.product.prodname_copilot %} in action. For more information, see the [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) website. 
+GitHub Copilot 提供的建议来自 OpenAI 使用数十亿行开放源代码构建的模型。 因此，{% data variables.product.prodname_copilot %} 的训练集可能包含不安全的编码模式、bug 或对过时 API 或习惯用语的引用。 当 {% data variables.product.prodname_copilot %} 基于此训练数据生成建议时，这些建议也可能包含不需要的模式。 
 
-GitHub Copilot offers suggestions from a model that OpenAI built from billions of lines of open source code. As a result, the training set for {% data variables.product.prodname_copilot %} may contain insecure coding patterns, bugs, or references to outdated APIs or idioms. When {% data variables.product.prodname_copilot %} produces suggestions based on this training data, those suggestions may also contain undesirable patterns. 
+你负责确保代码的安全性和质量。 建议你在使用由 {% data variables.product.prodname_copilot %} 生成的代码时采取与使用任何不是你自己编写的代码时相同的预防措施。 这些预防措施包括严格的测试、IP 扫描和安全漏洞跟踪。 {% data variables.product.company_short %} 提供了许多功能来帮助你监视和改进代码质量，例如 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_dependabot %}、{% data variables.product.prodname_codeql %} 和 {% data variables.product.prodname_code_scanning %}。 所有这些功能都可以在公共存储库中免费使用。 有关详细信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)”和“[{% data variables.product.company_short %} 安全功能](/code-security/getting-started/github-security-features)”。
 
-You are responsible for ensuring the security and quality of your code. We recommend you take the same precautions when using code generated by {% data variables.product.prodname_copilot %} that you would when using any code you didn't write yourself. These precautions include rigorous testing, IP scanning, and tracking for security vulnerabilities. {% data variables.product.company_short %} provides a number of features to help you monitor and improve code quality, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_codeql %} and {% data variables.product.prodname_code_scanning %}. All these features are free to use in public repositories. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)" and "[{% data variables.product.company_short %} security features](/code-security/getting-started/github-security-features)."
-
-{% data variables.product.prodname_copilot %} uses filters to block offensive words in the prompts and avoid producing suggestions in sensitive contexts. We are committed to constantly improving the filter system to more intelligently detect and remove offensive suggestions generated by {% data variables.product.prodname_copilot %}, including biased, discriminatory, or abusive outputs. If you see an offensive suggestion generated by {% data variables.product.prodname_copilot %}, please report the suggestion directly to copilot-safety@github.com so that we can improve our safeguards. 
+{% data variables.product.prodname_copilot %} 使用筛选器来阻止在提示中出现冒犯性词语，并避免在敏感上下文中生成建议。 我们致力于不断改进筛选系统，以便更智能地检测和删除 {% data variables.product.prodname_copilot %} 生成的冒犯性建议，包括有偏见的、歧视性的或滥用的输出。 如果有看到 {% data variables.product.prodname_copilot %} 生成的冒犯性建议，请直接将建议报告给 copilot-safety@github.com，以便我们改进保护措施。 
 
 {% data reusables.copilot.emus-cannot-use-copilot %}
 
-## About billing for {% data variables.product.prodname_copilot %}
+## 关于 {% data variables.product.prodname_copilot %} 的计费
 
-{% data variables.product.prodname_copilot %} is a paid feature, requiring a monthly or yearly subscription. Verified students, teachers, and maintainers of popular open source projects on {% data variables.product.prodname_dotcom %} are eligible to use {% data variables.product.prodname_copilot %} for free. If you meet the criteria for a free {% data variables.product.prodname_copilot %} subscription, you will be automatically notified when you visit the {% data variables.product.prodname_copilot %} subscription page. If you do not meet the criteria for a free {% data variables.product.prodname_copilot %} subscription, you will be offered a 60 day free trial, after which a paid subscription is required for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+{% data variables.product.prodname_copilot %} 是一项付费功能，需要按月或按年订阅。 {% data variables.product.prodname_dotcom %} 上热门的开放源代码项目的经过验证的学生、教师和维护人员有资格免费使用 {% data variables.product.prodname_copilot %}。 如果满足免费订阅 {% data variables.product.prodname_copilot %} 的条件，则在访问 {% data variables.product.prodname_copilot %} 订阅页面时会自动收到通知。 如果不满足免费订阅 {% data variables.product.prodname_copilot %} 的条件，你将获得 60 天的免费试用期，之后需要付费订阅才能继续使用。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_copilot %} 的计费](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)”。
 
-## About the license for the {% data variables.product.prodname_copilot %} plugin in JetBrains IDEs
+## 关于 JetBrains IDE 中 {% data variables.product.prodname_copilot %} 插件的许可证
 
-{% data variables.product.prodname_dotcom %}, Inc. is the licensor of the JetBrains plugin. The end user license agreement for this plugin is the [{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) and use of this plugin is subject to those terms. JetBrains has no responsibility or liability in connection with the plugin or such agreement. By using the plugin, you agree to the foregoing terms.
+{% data variables.product.prodname_dotcom %}, Inc. 是 JetBrains 插件的许可方。 此插件的最终用户许可协议为 [{% data variables.product.prodname_dotcom %} 附加产品和功能条款](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)，且此插件的使用受这些条款的约束。 JetBrains 对插件或此类协议不承担任何责任或义务。 使用插件即代表你同意上述条款。
 
-## Further reading
+## 延伸阅读
 
-- "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)"
+- [{% data variables.product.company_short %} 附加产品和功能条款](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)

translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md

@@ -80,7 +80,8 @@ Name | Description
 **`admin:enterprise`** | Gives full control of enterprise functionality. For more information, see "[Managing enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation.<br><br>Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`. 
 &emsp;`manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %}
 &emsp;`manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %}
-&emsp;`read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}
+&emsp;`read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}{% ifversion read-audit-scope %}
+**`read:audit_log`** | Read audit log data.{% endif %}
 {% note %}
 
 **Note:** Your OAuth App can request the scopes in the initial redirection. You

translations/zh-CN/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md

@@ -6,12 +6,12 @@ versions:
 topics:
   - Webhooks
 shortTitle: Receiving webhooks with the GitHub CLI
-ms.openlocfilehash: 2772a9d4208d0afe77871255ad6510b7f39de8d5
-ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.openlocfilehash: 11bc5b476a191a61594cb73f1e6ce1be5bb6cf9b
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 11/04/2022
-ms.locfileid: '148132961'
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160662'
 ---
 ## 关于使用 {% data variables.product.prodname_cli %} 接收 Webhook
 

translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md

@@ -20,6 +20,8 @@ As a discussions maintainer, you can create community resources to encourage dis
 
 When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
 
+You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
+
 For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
 
 {% data reusables.discussions.you-can-label-discussions %}
@@ -40,23 +42,63 @@ You can also move a discussion to a different category. It's not possible to mov
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
-  !["Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png)
+
+   ![Screenshot of the "Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png)
+
 1. Click a category.
-  !["Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png)
+
+   ![Screenshot of the "Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png)
 
 ## Pinning a discussion
 
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+{% ifversion discussions-category-specific-pins %}
+You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+
+This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+
+![Screenshot of a globally pinned discussion and a discussion pinned to the Ideas category](/assets/images/help/discussions/overview-pinned-discussions.png)
+
+### Pinning a discussion globally
+{% endif %}
+
+You can pin up to four important discussions above the list of discussions for the repository or organization. 
+
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
-  !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png)
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Pin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %}
+
+   ![Screenshot of the "Pin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png){% endif %}
+
 1. Optionally, customize the look of the pinned discussion.
-  ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
+   ![Screenshot of customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
 1. Click **Pin discussion**.
-  !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+   ![Screenshot of the "Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+{% ifversion discussions-category-specific-pins %}
+### Pinning a discussion to a category
+
+You can pin up to four important discussions above the list of discussions in a specific category. 
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+   
+   ![Screenshot of the "Pin discussion to CATEGORY" option in right sidebar for discussion](/assets/images/help/discussions/pin-discussion-to-category.png)
+
+2. To confirm, click **Pin to CATEGORY**.
+
+   ![Screenshot of the "Pin discussion to CATEGORY" modal](/assets/images/help/discussions/pin-discussion-to-category-modal.png)
+
+{% endif %}
 
 ## Editing a pinned discussion
 
@@ -66,21 +108,60 @@ Editing a pinned discussion will not change the discussion's category. For more
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
-  !["Edit pinned discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png)
+  {% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Edit pinned discussion" option in right sidebar for discussion](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png) {% else %}
+
+
+   ![Screenshot of the "Edit pinned discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png){% endif %}
+
 1. Customize the look of the pinned discussion.
-  ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
+  ![Screenshot of customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
 1. Click **Pin discussion**.
-  !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+  ![Screenshot of the "Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
 
 ## Unpinning a discussion
 
+{% ifversion discussions-category-specific-pins %}
+
+You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+
+### Unpinning a globally pinned discussion
+
+You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+{% endif %}
+
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
-  !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png)
+
+  ![Screenshot of the "Unpin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png)
+
 1. Read the warning, then click **Unpin discussion**.
-  !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png)
+
+  ![Screenshot of the "Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png)
+
+{% ifversion discussions-category-specific-pins %}
+### Unpinning a discussion from a category
+
+You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+
+   ![Screenshot of the "Unpin discussion from this category" option in right sidebar for discussion](/assets/images/help/discussions/unpin-discussion-from-category.png)
+
+1. Read the warning, then click **Unpin from this category**.
+
+   ![Screenshot of the "Unpin from this category" button in the "Unpin this discussion from this category" modal](/assets/images/help/discussions/unpin-discussion-from-category-modal.png)
+
+{% endif %}
 
 ## Transferring a discussion
 
@@ -89,12 +170,21 @@ To transfer a discussion, you must have permissions to create discussions in the
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**.
-  !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png)
+1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Transfer discussion" option in right sidebar for discussion](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %}
+
+  
+   ![Screenshot of the "Transfer discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png){% endif %}
+
 1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
-  !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
+
+   ![Screenshot of the "Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
+
 1. Click **Transfer discussion**.
-  !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png)
+
+   ![Screenshot of the "Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png)
 
 ## Deleting a discussion
 
@@ -102,9 +192,16 @@ To transfer a discussion, you must have permissions to create discussions in the
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
-  !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png)
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Delete discussion" option in right sidebar for discussion](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% else %}
+
+
+   ![Screenshot of the "Delete discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png){% endif %}
+
 1. Read the warning, then click **Delete this discussion**.
-  !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png)
+
+   ![Screenshot of the "Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png)
 
 ## Converting issues based on labels
 

translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md

@@ -1,41 +1,47 @@
 ---
-title: 主持讨论
-intro: '可以通过将评论标记为答案、锁定或解锁讨论、将问题转换为讨论，以及编辑或删除不符合{% ifversion fpt or ghec %}社区行为准则{% elsif ghes > 3.5 %}和组织的参与指南{% endif %}的评论、讨论和类别，来促进正常的协作。'
+title: Moderating discussions
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
   feature: discussions
-ms.openlocfilehash: 7d128c9beadb190f9c22c345cf0c3124b1dfcfcb
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147410113'
 ---
-## 关于主持讨论
 
-{% data reusables.discussions.about-discussions %}如果你对存储库具有会审权限，便可通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发早期阶段时将问题转换为讨论，从而帮助主持存储库的讨论。 同样，对于组织讨论，如果你对源存储库具有会审权限，则可以为该组织主持讨论。
 
-## 将评论标记为答案
+## About moderating discussions
+
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
+
+## Marking a comment as an answer
 
 {% data reusables.discussions.marking-a-comment-as-an-answer %}
 
-## 锁定讨论
+## Locking discussions
 
-如果整个对话没有建设性或者违反了社区的行为准则或 {% data variables.product.prodname_dotcom %} 的[社区准则](/free-pro-team@latest/github/site-policy/github-community-guidelines)，锁定对话是明智之举。 您还可以锁定对话，以防止对要用作社区公告的讨论发表评论。 锁定对话后，对存储库或组织讨论的源存储库具有写入访问权限的人员仍能够对讨论发表评论。
+It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion.
 
-{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %}
-1. 在讨论列表中，单击要锁定的讨论。
-  ![锁定讨论](/assets/images/help/discussions/unanswered-discussion.png)
-1. 单击讨论右侧的“锁定对话”。
-1. 阅读有关锁定对话的信息，然后单击“锁定此讨论的对话”。
-1. 准备好解锁对话时，请单击“解锁对话”，然后单击“解锁此讨论的对话” 。
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+1. In the list of discussions, click the discussion you want to lock.
+  ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png)
+1. In the right margin of a discussion, click **Lock conversation**.
+1. Read the information about locking conversations and click **Lock conversation on this discussion**.
+1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**.
 
-## 将议题转换为讨论
+## Converting an issue to a discussion
 
-在将议题转换为讨论时，会使用议题中的内容自动创建讨论。 对存储库或组织讨论的源存储库具有写入访问权限的人员可以根据标签批量转换问题。 有关详细信息，请参阅“[管理讨论](/discussions/managing-discussions-for-your-community/managing-discussions)”。
+When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
 
-{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.repositories.sidebar-issues %}
-1. 在议题列表中，单击您想要转换的议题。
-1. 单击问题右侧的“转换为讨论”。
-1. 选择“选择类别”下拉菜单，然后单击某个类别进行讨论。
-1. 单击“我明白，将此问题转化为讨论”。
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.repositories.sidebar-issues %}
+1. In the list of issues, click the issue you'd like to convert.
+1. In the right margin of an issue, click **Convert to discussion**.
+1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
+1. Click **I understand, convert this issue to a discussion**.
+
+{% ifversion discussions-hide-comments-on-block %}
+## Blocking a user from your organization
+
+Organization owners and moderators can block a user from the organization if their comments don't align with the community's code of conduct. When you block a user, they will no longer be able to comment on discussions. You can also hide all of the comments a user has made in the organization. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
+
+{% data reusables.organizations.blocking-a-user %} 
+{% endif %}

translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md

@@ -33,15 +33,16 @@ Once you are a verified {% data variables.product.prodname_global_campus %} stud
 - Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand.
 - Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)."
 
-A free subscription for {% data variables.product.prodname_copilot %} is available to verified students with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
-
-{% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
+{% data variables.product.prodname_global_campus %} students also receive the following {% data variables.product.prodname_dotcom %} benefits.
+- **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
+- **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
 
 {% note %}
 
 **Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
 
 {% endnote %}
+
 ## Further reading
 
 - "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)"

translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md

@@ -212,8 +212,8 @@ $ git remote rm destination
 # Remove remote
 $ git remote -v
 # Verify it's gone
-> origin  https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch)
-> origin  https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
 ```
 
 {% warning %}