Merge pull request #52314 from github/repo-sync

Repo sync

content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-labels-with-self-hosted-runners.md

@@ -17,7 +17,7 @@ For information on how to use labels to route jobs to specific types of self-hos
 
 {% data reusables.actions.self-hosted-runner-management-permissions-required %}
 
->[!NOTE]Action Runner Controller does not support multiple labels, to find our more please read our [Action Runner Controller documentation](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-actions-runner-controller#using-arc-runners-in-a-workflow)
+>[!NOTE]Actions Runner Controller does not support multiple labels, to find out more please read our [Actions Runner Controller documentation](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-actions-runner-controller#using-arc-runners-in-a-workflow)
 
 ## Creating a custom label
 

content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md

@@ -17,7 +17,7 @@ shortTitle: Use runners in a workflow
 
 You can target self-hosted runners for use in a workflow based on the labels assigned to the runners{% ifversion target-runner-groups %}, or their group membership, or a combination of these{% endif %}.
 
->[!NOTE]Action Runner Controller does not support multiple labels, only the name of the runner can be used in place of a label
+>[!NOTE]Actions Runner Controller does not support multiple labels, only the name of the runner can be used in place of a label
 
 ## About self-hosted runner labels
 

content/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows.md

@@ -809,7 +809,7 @@ on:
 
 {% note %}
 
-**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request_target)." By default, a workflow only runs when a `pull_request_target` event's activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows by different activity types, use the `types` keyword. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onevent_nametypes)."
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request)." By default, a workflow only runs when a `pull_request_target` event's activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows by different activity types, use the `types` keyword. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onevent_nametypes)."
 
 {% endnote %}
 

content/authentication/connecting-to-github-with-ssh/managing-deploy-keys.md

@@ -129,10 +129,10 @@ Since {% data variables.product.prodname_github_apps %} are a first class actor
 
 ### Pros of installation access tokens
 
-* Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API).
-* Dedicated rate limits that grow with your organization.
-* Decoupled from {% data variables.product.prodname_dotcom %} user identities, so they do not consume any licensed seats.
-* Never granted a password, so cannot be directly signed in to.
+* Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API)
+* Dedicated rate limits that grow with your organization
+* Decoupled from {% data variables.product.prodname_dotcom %} user identities, so they do not consume any licensed seats
+* Never granted a password, so cannot be directly signed in to
 
 ### Cons of installation access tokens
 

content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-mandatory-two-factor-authentication.md

@@ -14,12 +14,12 @@ shortTitle: About mandatory 2FA
 ## About eligibility for mandatory 2FA
 
 Your account is selected for mandatory 2FA if you have taken some action on {% data variables.product.product_name %} that shows you are a contributor. Eligible actions include:
-* Publishing an app or action for others.
-* Creating a release for your repository.
-* Contributing to specific high-importance repositories, such as [the projects tracked by the Open Source Security Foundation](https://github.com/ossf/wg-securing-critical-projects#current-work).
-* Being an administrator of a high-importance repository.
-* Being an organization owner for an organization containing repositories or other users.
-* Being an enterprise administrator.
+* Publishing an app or action for others
+* Creating a release for your repository
+* Contributing to specific high-importance repositories, such as [the projects tracked by the Open Source Security Foundation](https://github.com/ossf/wg-securing-critical-projects#current-work)
+* Being an administrator of a high-importance repository
+* Being an organization owner for an organization containing repositories or other users
+* Being an enterprise administrator
 
 {% data variables.product.prodname_dotcom %} is continually assessing improvements to our account security features and 2FA requirements, so these criteria may change over time.
 

content/code-security/secret-scanning/introduction/about-secret-scanning.md

@@ -54,7 +54,7 @@ Below is a typical workflow that explains how {% data variables.product.prodname
 
 * **Review**: When a secret is detected, you'll need to review the alert details provided.
 
-* **Remediation**: You then need take appropriate actions to remediate the exposure. This might include:
+* **Remediation**: You then need to take appropriate actions to remediate the exposure. This might include:
   * Rotating the affected credential to ensure it is no longer usable.
   * Removing the secret from the repository's history (using tools like BFG Repo-Cleaner or {% data variables.product.prodname_dotcom %}'s built-in features).
 

content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md

@@ -112,7 +112,7 @@ Hi, I'm Mona. You might recognize me as {% data variables.product.prodname_dotco
 
 ## Adding a collapsed section
 
-To keep your content tidy, you can use the `<details>` tag to create an expandible collapsed section.
+To keep your content tidy, you can use the `<details>` tag to create an expandable collapsed section.
 
 1. To create a collapsed section for the table you created, wrap your table in `<details>` tags like in the following example.
 

content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md

@@ -49,16 +49,16 @@ There's no minimum Git version necessary to interact with {% data variables.prod
 
 ### Ensure the remote is correct
 
-The repository you're trying to fetch must exist on {% data variables.location.product_location %}, and the URL is case-sensitive.
+The repository you're trying to fetch must exist on {% data variables.location.product_location %}.
 
 You can find the URL of the local repository by opening the command line and
 typing `git remote -v`:
 
 ```shell
 $ git remote -v
 # View existing remotes
-> origin  https://github.com/ghost/reactivecocoa.git (fetch)
-> origin  https://github.com/ghost/reactivecocoa.git (push)
+> origin  https://github.com/ghost/cocoareactive.git (fetch)
+> origin  https://github.com/ghost/cocoareactive.git (push)
 
 $ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git
 # Change the 'origin' remote's URL

data/reusables/actions/jobs/section-defining-outputs-for-jobs.md

@@ -4,6 +4,8 @@ You can use `jobs.<job_id>.outputs` to create a `map` of outputs for a job. Job
 
 Job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}.
 
+If an output is skipped because it may contain a secret, you will see the following warning message: "Skip output `{output.Key}` since it may contain secret." For more information on how to handle secrets, please refer to the [Example: Masking and passing a secret between jobs or workflows](/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#example-masking-and-passing-a-secret-between-jobs-or-workflows).
+
 To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[AUTOTITLE](/actions/learn-github-actions/contexts#needs-context)."
 
 ### Example: Defining outputs for a job

data/reusables/actions/self-hosted-runner-labels-runs-on.md

@@ -2,4 +2,4 @@ To specify a self-hosted runner for your job, configure `runs-on` in your workfl
 
 Self-hosted runners may have the `self-hosted` label. When setting up a self-hosted runner, by default we will include the label `self-hosted`. You may pass in the `--no-default-labels` flag to prevent the self-hosted label from being applied. Labels can be used to create targeting options for runners, such as operating system or architecture, we recommend providing an array of labels that begins with `self-hosted` (this must be listed first) and then includes additional labels as needed. When you specify an array of labels, jobs will be queued on runners that have all the labels that you specify.
 
-Note that Action-runner-controller does not support multiple labels and does not support the `self-hosted` label.
+Note that Actions Runner Controller does not support multiple labels and does not support the `self-hosted` label.

data/reusables/two_fa/mandatory-2fa-contributors-2023-nested.md

@@ -1 +1 @@
-As of March 2023, {% data variables.product.prodname_dotcom %} began to require all users who contribute code on {% data variables.product.prodname_dotcom_the_website %} to enable one or more forms of two-factor authentication (2FA). If you were in an eligible group, you would have received a notification email when that group was selected for enrollment, marking the beginning of a 45-day 2FA enrollment period, and you would have seen banners asking you to enroll in 2FA on {% data variables.product.prodname_dotcom_the_website %}. If you didn't receive a notification, then you were not part of a group required to enable 2FA, though we strongly recommend it.
+As of March 2023, {% data variables.product.prodname_dotcom %} required all users who contribute code on {% data variables.product.prodname_dotcom_the_website %} to enable one or more forms of two-factor authentication (2FA). If you were in an eligible group, you would have received a notification email when that group was selected for enrollment, marking the beginning of a 45-day 2FA enrollment period, and you would have seen banners asking you to enroll in 2FA on {% data variables.product.prodname_dotcom_the_website %}. If you didn't receive a notification, then you were not part of a group required to enable 2FA, though we strongly recommend it.