Merge branch 'main' into repo-sync

Author: Octomerger

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)."
 

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.