#github-actions (2022-10)
Discussions related to GitHub Actions
2022-10-01
2022-10-03
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
GitHub Actions: Jobs running on macos-latest
are now running on macOS 12
2022-10-04
Introducing Actions on GitHub Mobile Introducing Actions on GitHub Mobile
Introducing Actions on GitHub Mobile
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;
3.1.0 just released https://github.com/actions/checkout/releases/tag/v3.1.0
try pinning to 3.0.2
it look like that is it
2022-10-11
GitHub Actions: Deprecating save-state and set-output commands GitHub Actions: Deprecating save-state and set-output commands
GitHub Actions: Deprecating save-state and set-output commands
2022-10-12
GitHub Actions: larger Hosted Runners now support -latest
tag
GitHub Actions: larger Hosted Runners now support -latest
tag
GitHub Actions: larger Hosted Runners now support -latest
tag
2022-10-13
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
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
echo "{environment_variable_name}={value}" >> $GITHUB_ENV
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
Design improvements to GitHub Actions navigation Design improvements to GitHub Actions navigation
Design improvements to GitHub Actions navigation
2022-10-18
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
GitHub Actions:OpenID Connect support enhanced to enable secure cloud deployments at scale
2022-10-20
GitHub Actions: larger hosted runners are now automatically created for customers GitHub Actions: larger hosted runners are now automatically created for customers
GitHub Actions: larger hosted runners are now automatically created for customers
Manage caches in your Actions workflows from Web Interface Manage caches in your Actions workflows from Web Interface
Manage caches in your Actions workflows from Web Interface