CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 13:24:54 GMT
server: Fly/6f91d33b9d (2025-10-08)
content-type: text/html; charset=utf-8
content-encoding: gzip
via: 2 fly.io, 2 fly.io
fly-request-id: 01K79Q46RX6CA8YC356VKKW153-bom
Set environment variables for all steps in a GitHub Action | Simon Willison’s TILs
Set environment variables for all steps in a GitHub Action
From this example I learned that you can set environment variables such that they will be available in ALL jobs once at the top of a workflow:
name: Build and Deploy to Cloud Run
on:
push:
branches:
- master
env:
PROJECT_ID: ${{ secrets.RUN_PROJECT }}
RUN_REGION: us-central1
SERVICE_NAME: helloworld-nodejs
I had previously been using this much more verbose pattern:
- name: Fetch projects
env:
BIGLOCAL_TOKEN: ${{ secrets.BIGLOCAL_TOKEN }}
run: python fetch_projects.py dbs/biglocal.db $BIGLOCAL_TOKEN --contact ...
Related
- github-actions Only run GitHub Action on push to master / main - 2020-04-19
- github-actions Deploying a live Datasette demo when the tests pass - 2022-03-27
- github-actions Running different steps on a schedule - 2020-04-20
- github-actions Running tests against PostgreSQL in a service container - 2021-02-23
- github-actions Dump out all GitHub Actions context - 2020-04-19
- github-actions Conditionally running a second job in a GitHub Actions workflow - 2022-07-11
- cloudrun Using build-arg variables with Cloud Run deployments - 2021-11-19
- googlecloud Workaround for google-github-actions/setup-gcloud errors - 2022-12-01
- github-actions Talking to a PostgreSQL service container from inside a Docker container - 2020-09-18
- github-actions Installing different PostgreSQL server versions in GitHub Actions - 2021-07-05
Created 2020-04-19T07:55:08-07:00 · Edit