Merge branch 'main' into repo-sync

content/actions/creating-actions/creating-a-docker-container-action.md

@@ -96,7 +96,7 @@ runs:
 ```
 {% endraw %}
 
-This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you must declare the input using `inputs` and pass the input in the `args` keyword.
+This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you should declare the input using `inputs` and pass the input in the `args` keyword. Everything you include in `args` is passed to the container, but for better discoverability for users of your action, we recommended using inputs.
 
 {% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image.
 

content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md

@@ -91,6 +91,7 @@ Your access token will require the following scope:
 
 - For private repositories, use an access token with the [`repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
 - For public repositories, use an access token with the [`public_repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
+- For organizations, use an access token with the [`admin:org` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
 
 To  authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions:
 - For repositories, assign the `administration` permission.

content/actions/using-workflows/workflow-commands-for-github-actions.md

@@ -309,7 +309,7 @@ jobs:
 ::add-mask::{value}
 ```
 
-Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`.
+Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`. When you mask a value, it is treated as a secret and will be redacted on the runner. For example, after you mask a value, you won't be able to set that value as an output.
 
 ### Example: Masking a string
 

content/rest/overview/resources-in-the-rest-api.md

@@ -449,7 +449,7 @@ If you exceed the rate limit, an error response returns:
 If your OAuth App needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route.
 
 ```shell
-$ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
+$ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre %}/user/repos
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 5000

content/rest/reference/pulls.md

@@ -14,5 +14,5 @@ miniTocMaxHeadingLevel: 3
 ---
 
 <!--
-  Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/projects
--->
+  Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/pulls/
+-->

data/reusables/actions/workflow-dispatch-inputs.md

@@ -34,5 +34,5 @@ jobs:
     if: {% raw %} ${{ github.event.inputs.print_tags == 'true' }} {% endraw %}
     steps:
       - name: Print the input tag to STDOUT
-        run: echo {% raw %} The tag is ${{ github.event.inputs.tag }} {% endraw %}
+        run: echo {% raw %} The tags are ${{ github.event.inputs.tags }} {% endraw %}
 ```