Skip to content

Deploy jobs use GitHub environments #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
byteful merged 1 commit into from
Oct 5, 2026
Merged

Deploy jobs use GitHub environments #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .github/workflows/deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,11 @@ jobs:
deploy:
name: build + publish civfix-admin
runs-on: ubuntu-latest
# One expression decides both (the YAML alias below), so a production deploy always waits for
# reviewer approval and can never run from a ref other than main or a v* tag.
environment: &deploy_env ${{ startsWith(github.ref, 'refs/tags/v') && 'production' || 'staging' }}
env:
DEPLOY_ENV: ${{ startsWith(github.ref, 'refs/tags/v') && 'production' || 'staging' }}
DEPLOY_ENV: *deploy_env
steps:
- name: Refuse a deploy from any ref but main or a v* release tag
# The Pages branch below decides production-vs-preview, so the set of refs that can reach it has
Expand Down
Loading