[GA date TBD] Update reusable workflows docs for GA (#22795)

* Update reusable workflows docs

* Update content/actions/learn-github-actions/reusing-workflows.md

Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>

* Update content/actions/learn-github-actions/reusing-workflows.md

* Update content/actions/learn-github-actions/reusing-workflows.md

* Update content/actions/learn-github-actions/reusing-workflows.md

Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>

* Update content/actions/learn-github-actions/reusing-workflows.md

Co-authored-by: Martin Lopes <martin389@github.com>

* Apply review suggestion from Lucas

* Update content/actions/learn-github-actions/reusing-workflows.md

Co-authored-by: Martin Lopes <martin389@github.com>

* Update content/actions/learn-github-actions/reusing-workflows.md

Co-authored-by: Martin Lopes <martin389@github.com>

* Update content/actions/learn-github-actions/reusing-workflows.md

Co-authored-by: Martin Lopes <martin389@github.com>

* Add information about use of runners

As per review comment from Ajay Krishna Nalisetty

* Update content/actions/learn-github-actions/workflow-syntax-for-github-actions.md

Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>

* Update content/actions/learn-github-actions/workflow-syntax-for-github-actions.md

* Fix version as per Lucas's review comment

* Explain using environment secrets

* Add workflow diagram

* Move explanation of diagram above it

* Slight change to job_workflow-ref description

Include the syntax of the response data, as per
https://github.slack.com/archives/C01SMLA6MNY/p1637731982336700

* Clarify difference between repo and job_workflow_ref

Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
Co-authored-by: Martin Lopes <martin389@github.com>
Co-authored-by: Octomerger Bot <63058869+Octomerger@users.noreply.github.com>

Author: 4 people

assets/images/help/images/reusable-workflows-ci-cd.png

@@ -18,12 +18,6 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% note %}
-
-**Note:** Reusable workflows are currently in beta and subject to change.
-
-{% endnote %}
-
 ## About reusable workflows
 
 Rather than copying and pasting deployment jobs from one workflow to another, you can create a reusable workflow that performs the deployment steps. A reusable workflow can be used by another workflow if it meets one of the access requirements described in "[Reusing workflows](/actions/learn-github-actions/reusing-workflows#access-to-reusable-workflows)."

content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md

@@ -68,7 +68,9 @@ In addition to the usage limits, you must ensure that you use {% data variables.
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## Billing for reusable workflows
 
-If you reuse a workflow, billing is always associated with the caller workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dotcom %}-hosted runners{% endif %}{% ifversion ghae %}{% data variables.actions.hosted_runner %}s{% endif %} is always evaluated using only the caller's context. The caller cannot use {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dotcom %}-hosted runners{% endif %}{% ifversion ghae %}{% data variables.actions.hosted_runner %}s{% endif %} from the called repository. 
+
+For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
 ## Artifact and log retention policy

content/actions/learn-github-actions/reusing-workflows.md

@@ -226,6 +226,31 @@ For more information, see "[Reusing workflows](/actions/learn-github-actions/reu
 
 Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`.
 
+## `on.workflow_call.outputs`
+
+A map of outputs for a called workflow. Called workflow outputs are available to all downstream jobs in the caller workflow. Each output has an identifier, an optional `description,` and a `value.` The `value` must be set to the value of an output from a job within the called workflow.
+
+In the example below, two outputs are defined for this reusable workflow: `workflow_output1` and `workflow_output2`. These are mapped to outputs called `job_output1` and `job_output2`, both from a job called `my_job`.
+
+### Example
+
+{% raw %}
+```yaml
+on:
+  workflow_call:
+    # Map the workflow outputs to job outputs
+    outputs:
+      workflow_output1:
+        description: "The first job output"
+        value: ${{ jobs.my_job.outputs.job_output1 }}
+      workflow_output2:
+        description: "The second job output"
+        value: ${{ jobs.my_job.outputs.job_output2 }}  
+```
+{% endraw %}
+
+For information on how to reference a job output, see [`jobs.<job_id>.outputs`](#jobsjob_idoutputs). For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
 ## `on.workflow_call.secrets`
 
 A map of the secrets that can be used in the called workflow.

content/actions/learn-github-actions/usage-limits-billing-and-administration.md

@@ -77,7 +77,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% ifversion fpt or ghec %}
 | [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}
 | [`team`](#team-category-actions) | Contains all activities related to teams in your organization.
-| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.
+| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
+| [`workflows`](#workflows-category-actions) | Contains activities related to {% data variables.product.prodname_actions %} workflows.{% endif %}
 
 You can search for specific sets of actions using these terms. For example:
 
@@ -743,10 +744,11 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)."
 | `enable` | Triggered when an organization owner enables team discussions for an organization.
 
+{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}
 ### `workflows` category actions
 
 {% data reusables.actions.actions-audit-events-workflow %}
-
+{% endif %}
 ## Further reading
 
 - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}

content/actions/learn-github-actions/workflow-syntax-for-github-actions.md

@@ -7,6 +7,6 @@
 | `disable_workflow` | Triggered when a workflow is disabled.
 | `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.
 | `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
-| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %}
+| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %}
 | `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
 | `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."{% endif %}

content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md

@@ -0,0 +1,13 @@
+To pass named inputs to a called workflow, use the `with` keyword in a job. Use the `secrets` keyword to pass named secrets. For inputs, the data type of the input value must match the type specified in the called workflow (either boolean, number, or string).
+
+{% raw %}
+```yaml
+jobs:
+  call-workflow-passing-data:
+    uses: octo-org/example-repo/.github/workflows/reusable-workflow.yml@main
+    with:
+      username: mona
+    secrets:
+      envPAT: ${{ secrets.envPAT }}
+```
+{% endraw %}