Actions bug fix hour for the week of April 15, 2023 (#37144)

Author: jc-clark

content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md

@@ -46,14 +46,6 @@ Third-party systems can be observability systems, change management systems, cod
 
 {% endif %}
 
-{% ifversion fpt %}
-{% note %}
-
-**Note:** Deployment protection rules are only available in **public** repositories if you are using {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, or {% data variables.product.prodname_team %}. For access to deployment protection rules in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. For more information on switching your subscription, see "[AUTOTITLE](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
-
-{% endnote %}
-{% endif %}
-
 ### Required reviewers
 
 Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed.

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

@@ -690,6 +690,8 @@ For built-in shell keywords, we provide the following defaults that are executed
 
 A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case.
 
+Input parameters defined for a Docker container must use `args`. For more information, see "[`jobs.<job_id>.steps[*].with.args`](#jobsjob_idstepswithargs)."
+
 ### Example of `jobs.<job_id>.steps[*].with`
 
 Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables.

data/reusables/actions/actions-secrets-variables-repository-access.md

@@ -1 +1,10 @@
+
+{% ifversion fpt %}
+{% note %}
+
+**Note:** Organization-level secrets and variables are not available to be used by private repositories for your plan. For more information on upgrading your {% data variables.product.company_short %} subscription, see "[AUTOTITLE](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)".
+
+{% endnote %}
+{% endif %}
+
 When creating a secret or variable in an organization, you can use a policy to limit access by repository. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.