From 49c26d412acc258cf6ce507cc983d4428b7e7adf Mon Sep 17 00:00:00 2001 From: Mikkel Jakobsen Date: Fri, 8 Dec 2023 10:13:53 +0100 Subject: [PATCH] Fix branch change GH workflow YAML formatting --- .../create-release-on-branch-changes.yml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/.github/workflows/create-release-on-branch-changes.yml b/.github/workflows/create-release-on-branch-changes.yml index b1ef6a026..ebdb77b76 100644 --- a/.github/workflows/create-release-on-branch-changes.yml +++ b/.github/workflows/create-release-on-branch-changes.yml @@ -13,6 +13,11 @@ jobs: steps: - name: Set release variables id: resolve-release-vars + # Version 0.0.0-SHA is a schema that supports semantic versioning but + # should sink below proper versions. + # Output package.json to provide insight and help debugging + # Using branch names as tags allows other projects to track unreleased + # development. run: | RELEASE_BRANCH=$(echo ${GITHUB_REF#refs/heads/}) RELEASE_SHA=${{ github.sha }} @@ -20,11 +25,6 @@ jobs: echo "RELEASE_BRANCH=$RELEASE_BRANCH" >> "$GITHUB_ENV" echo "RELEASE_SHA=$RELEASE_SHA" >> "$GITHUB_ENV" echo "TAG_NAME=$TAG_NAME" >> "$GITHUB_ENV" - # Version 0.0.0-SHA is a schema that supports semantic versioning but - # should sink below proper versions. - # Output package.json to provide insight and help debugging - # Using branch names as tags allows other projects to track unreleased - # development. echo "NPM_VERSION=0.0.0-${RELEASE_SHA}" >> "$GITHUB_ENV" echo "DIST_FILENAME=dist-$RELEASE_BRANCH.zip" >> "$GITHUB_ENV" @@ -94,7 +94,7 @@ jobs: - name: Adding summary run: | - echo " - - - Npm package created 🚀. Version: ${{ env.NPM_VERSION }}" >> $GITHUB_STEP_SUMMARY + echo " + + + Npm package created 🚀. Version: ${{ env.NPM_VERSION }}" >> $GITHUB_STEP_SUMMARY