Merge branch 'main' into warn-about-renaming-action-branches

Author: janiceilene

content/actions/reference/encrypted-secrets.md

@@ -126,7 +126,11 @@ You can check which access policies are being applied to a secret in your organi
 
 ### Using encrypted secrets in a workflow
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
+
+**Note:** {% data reusables.actions.forked-secrets %}
+
+{% endnote %}
 
 To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 

content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md

@@ -19,6 +19,14 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also add an SSH key using the {% data variables.product.prodname_cli %}. For more information, see "[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. Copy the SSH public key to your clipboard.

content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md

@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %} 
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. In the "Pull requests" list, click the pull request you'd like to mark as ready for review.
 3. In the merge box, click **Ready for review**.

content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md

@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Modifying an active pull request locally
 
 {% data reusables.repositories.sidebar-pr %}

content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md

@@ -19,6 +19,14 @@ You can specify which branch you'd like to merge your changes into when you crea
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Changing the branch range and destination repository
 
 By default, pull requests are based on the parent repository's default branch. For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."

content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md

@@ -25,6 +25,14 @@ You can't merge a draft pull request. For more information about draft pull requ
 
 If you decide you don't want the changes in a topic branch to be merged to the upstream branch, you can [close the pull request](/articles/closing-a-pull-request) without merging.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Merging a pull request on {% data variables.product.prodname_dotcom %}
 
 {% data reusables.repositories.sidebar-pr %}

data/reusables/actions/forked-secrets.md

@@ -1 +1 @@
-With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.
+With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.