From 7b7ddcd4121e115839f093c55a27b2b74ed22c0c Mon Sep 17 00:00:00 2001 From: Wolfram Sokollek <8589105+WolfSoko@users.noreply.github.com> Date: Mon, 10 Jun 2024 19:06:58 +0200 Subject: [PATCH] docs: add info how to access monorepo path outputs (#1003) Added description how to access monorepo step result outputs using [] syntax It took me several hours to figure out how to access the outputs of these monorepo packages. Hopefully, this will save others some time --------- Signed-off-by: Wolfram Sokollek <8589105+WolfSoko@users.noreply.github.com> Co-authored-by: Jeff Ching --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 17792de..400a0eb 100644 --- a/README.md +++ b/README.md @@ -200,6 +200,14 @@ This prefix allows you to distinguish values for different releases. | `--patch` | Number representing patch semver value | | `--sha` | sha that a GitHub release was tagged at | +If the path contains `/` you can access the outputs by using javascript like property access `steps.release.outputs[--...]` +e.g.: + +```yaml +run: npm publish --workflow packages/my-module +if: ${{ steps.release.outputs['packages/my-module--release_created'] }} +``` + ## How release please works Release Please automates CHANGELOG generation, the creation of GitHub releases,