Chapter 9: GitHub Actions Hands-On
9.10 Environment-specific configs in CI
Use GitHub Environments (when available) for staging vs production secrets and optional protection rules. Keep names obvious: staging, production.
Never put production database passwords in the PR job. PR jobs should use disposable credentials or mocks.
What you see: a deploy job that declares environment: staging shows that name in the Actions UI — useful audit trail for your notes.