set-output can be used to define outputs for steps. The outputs can then be used in later steps and evaluated in with and env input sections. Also, the step returning outputs should have an id, which is referred to by the step consuming the outputs. The following is what that would look like for your … Read more
The original answer to this question used the Actions runner function set-env. Due to a security vulnerability set-env is being deprecated and should no longer be used. This is the new way to set environment variables. name: my workflow on: push jobs: build: runs-on: ubuntu-latest steps: – uses: actions/checkout@v2 – name: Set env run: echo … Read more
actions/checkout@v2 Version 2 of checkout resolves the detached HEAD state issue and simplifies pushing to origin. name: Push commit on: push jobs: report: runs-on: ubuntu-latest steps: – uses: actions/checkout@v2 – name: Create report file run: date +%s > report.txt – name: Commit report run: | git config –global user.name ‘Your Name’ git config –global user.email … Read more
I added a separate step for extracting branch name from $GITHUB_REF and set it to the step output – name: Extract branch name shell: bash run: echo “##[set-output name=branch;]$(echo ${GITHUB_REF#refs/heads/})” id: extract_branch after that, I can use it in the next steps with – name: Push to ECR id: ecr uses: jwalton/gh-ecr-push@master with: access-key-id: ${{ … Read more