From f48272235c28535fa45b6341ee3e8d31022ad301 Mon Sep 17 00:00:00 2001 From: Jacob Wallraff Date: Fri, 15 Dec 2023 09:34:59 -0800 Subject: [PATCH 1/2] Add note about job output scope (#47858) Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com> --- .../actions/jobs/section-defining-outputs-for-jobs.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md index c71df3e28f38..500bb1bf9c50 100644 --- a/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md +++ b/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md @@ -6,6 +6,12 @@ Job outputs containing expressions are evaluated on the runner at the end of eac To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[AUTOTITLE](/actions/learn-github-actions/contexts#needs-context)." +{% note %} + +**Note:** `$GITHUB_OUTPUT` is shared between all steps in a job. If you use the same output name in multiple steps, the last step to write to the output will override the value. If your job uses a matrix and writes to `$GITHUB_OUTPUT`, the content will be overwritten for each matrix combination. You can use the `matrix` context to create unique output names for each job configuration. For more information, see "[AUTOTITLE](/actions/learn-github-actions/contexts#matrix-context)." + +{% endnote %} + ### Example: Defining outputs for a job {% raw %} From b8b119e30d81c11de1ade834ea50d741fcba849a Mon Sep 17 00:00:00 2001 From: Ben Ahmady <32935794+subatoi@users.noreply.github.com> Date: Fri, 15 Dec 2023 17:37:11 +0000 Subject: [PATCH 2/2] Removes 'Schema enforcement' section (#47907) --- .../writing-for-github-docs/versioning-documentation.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/contributing/writing-for-github-docs/versioning-documentation.md b/content/contributing/writing-for-github-docs/versioning-documentation.md index 9835efe53c57..18093dfbb1f5 100644 --- a/content/contributing/writing-for-github-docs/versioning-documentation.md +++ b/content/contributing/writing-for-github-docs/versioning-documentation.md @@ -242,10 +242,6 @@ versions: feature: 'some-new-feature' ``` -### Schema enforcement - -The schema for validating the feature versioning lives in [`src/content-linter/lib/feature-versions-schema.js`](https://github.com/github/docs/blob/main/src/content-linter/lib/feature-versions-schema.js) and is exercised by [`tests/linting/lint-versioning.js`](https://github.com/github/docs/blob/main/src/content-linter/tests/lint-versioning.js). - ## Best practices Versioned content impacts the reader, but also impacts anyone who contributes to or reviews the content. Here are a few tips to improve the writing, reading, and reviewing experience for versioning syntax. None of these practices are mandatory and you will find edge and corner cases, but they're intended as useful heuristics to help you think through versioning.