#github-actions (2022-10)
Discussions related to GitHub Actions
2022-10-01
2022-10-03
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
GitHub Actions: Jobs running on macos-latest
are now running on macOS 12
GitHub Actions: Jobs running on macos-latest
are now running on macOS 12
![attachment image](https://github.blog/wp-content/uploads/2022/04/Engineering-Security.png?fit=1200%2C630)
GitHub Actions: Jobs running on macos-latest
are now running on macOS 12
2022-10-04
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
Introducing Actions on GitHub Mobile Introducing Actions on GitHub Mobile
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
anyone have seen this error before?
Run actions/checkout@v3
with:
repository: runatlantis/atlantis
token: ***
ssh-strict: true
persist-credentials: true
clean: true
fetch-depth: 1
lfs: false
submodules: false
set-safe-directory: true
/usr/bin/docker exec 9ff28c2640f36d36de6e5ae0ffe0378b7672e7045472288278dc5a2f66516c22 sh -c "cat /etc/*release | grep ^ID"
##[debug]ID=debian
##[debug]Running JavaScript Action with default external tool: node16
node:internal/fs/utils:344
throw err;
![RB avatar](https://avatars.slack-edge.com/2020-02-26/958727689603_86844033e59114029b3c_72.png)
3.1.0 just released https://github.com/actions/checkout/releases/tag/v3.1.0
![RB avatar](https://avatars.slack-edge.com/2020-02-26/958727689603_86844033e59114029b3c_72.png)
try pinning to 3.0.2
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
it look like that is it
2022-10-11
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
GitHub Actions: Deprecating save-state and set-output commands GitHub Actions: Deprecating save-state and set-output commands
![attachment image](https://github.blog/wp-content/uploads/2022/04/Engineering-Security.png?fit=1200%2C630)
GitHub Actions: Deprecating save-state and set-output commands
2022-10-12
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
GitHub Actions: larger Hosted Runners now support -latest
tag
GitHub Actions: larger Hosted Runners now support -latest
tag
![attachment image](https://user-images.githubusercontent.com/56982181/195146229-9b2550fa-6eea-472d-8f59-f53895e8ad8c.png)
GitHub Actions: larger Hosted Runners now support -latest
tag
2022-10-13
![emem avatar](https://avatars.slack-edge.com/2020-12-02/1551004246900_d6f2b7fd5964834308d2_72.jpg)
Hi folks. I am not sure if this is the right place to ask. I am having a hard time using the value of an env variable in another step in my github action workflow
jobs:
staging_environment:
runs-on: ubuntu:latest
- name: BuildandPush
id: build-and-push
uses: docker/build-push-action@v2
env:
REPOSITORY_URI: ${{ steps.login-ecr.outputs.registry }}
IMAGE_TAG: ${{ github.head_ref || github.ref_name }}-${{ github.sha }}
- name: update image
run: |
echo $IMAGE_TAG
I will like to be able to reuse the value of from IMAGE_TAG from previous steps
![managedkaos avatar](https://secure.gravatar.com/avatar/f7d88a7a95990c984ab107b491b51b3f.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0025-72.png)
I think you will need to use this approach to set the env variable: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable
![managedkaos avatar](https://secure.gravatar.com/avatar/f7d88a7a95990c984ab107b491b51b3f.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0025-72.png)
echo "{environment_variable_name}={value}" >> $GITHUB_ENV
![managedkaos avatar](https://secure.gravatar.com/avatar/f7d88a7a95990c984ab107b491b51b3f.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0025-72.png)
I would have three steps:
- first set the IMAGE_TAG env variable
- Use the IMAGE_TAG env var as input to
docker/build-push-action
env section - Use the same IMAGE_TAG env var later on in the workflow
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
Design improvements to GitHub Actions navigation Design improvements to GitHub Actions navigation
![attachment image](https://user-images.githubusercontent.com/6574688/195638749-99063333-205c-4a93-b83a-55617e7eb262.png)
Design improvements to GitHub Actions navigation
2022-10-18
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
GitHub Actions:OpenID Connect support enhanced to enable secure cloud deployments at scale GitHub Actions:OpenID Connect support enhanced to enable secure cloud deployments at scale
![attachment image](https://github.blog/wp-content/uploads/2022/04/Engineering-Security.png?fit=1200%2C630)
GitHub Actions:OpenID Connect support enhanced to enable secure cloud deployments at scale
2022-10-20
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
GitHub Actions: larger hosted runners are now automatically created for customers GitHub Actions: larger hosted runners are now automatically created for customers
![attachment image](https://github.blog/wp-content/uploads/2022/04/Engineering-Security.png?fit=1200%2C630)
GitHub Actions: larger hosted runners are now automatically created for customers
![actions Archives | The GitHub Blog avatar](https://a.slack-edge.com/80588/img/services/rss_72.png)
Manage caches in your Actions workflows from Web Interface Manage caches in your Actions workflows from Web Interface
![attachment image](https://github.blog/wp-content/uploads/2022/04/Engineering-Security.png?fit=1200%2C630)
Manage caches in your Actions workflows from Web Interface