gcp-cloud-run-github-actionslisted

Standardize GitHub Actions workflows for deploying containerized services to Google Cloud Run with authentication, image caching, multi-job pipelines, and post-deploy validation. ## When to use - Setting up CI/CD pipelines to deploy services to Google Cloud Run - Deploying multiple services (backend, worker, frontend) from a monorepo - Configuring Cloud Run services with VPC connectors, Cloud SQL instances, and environment variables - Implementing one-image-many-roles pattern (same Docker image, different MODE env var) - Optimizing build times by skipping rebuilds when images already exist in the registry - Adding post-deployment sanity checks to validate service health - Configuring per-environment (dev/staging/prod) Cloud Run settings (min/max instances, memory, CPU) - Authenticating GitHub Actions to GCP using service account keys or Workload Identity Federation - Deploying frontend apps with build-time environment variables ## Core conventions 1. **GitHub Actions authentication via `google-github-actions/auth@v2`**: use `credentials_json: "${{ vars.GCP_SA_KEY }}"` for service account key-based auth, or `workload_identity_provider` + `service_account` for Workload Identity Federation (preferred for security). Set `project_id: ${{ vars.GCP_PROJECT_ID }}` to scope the session. 2. **Setup gcloud CLI via `google-github-actions/setup-gcloud@v2`**: after authentication, configure gcloud with `project_id: ${{ vars.GCP_PROJECT_ID }}` to enable `gcloud run deploy` commands. 3