Create cloudrun.yml

[ngoiyaeric]

PR Type

Enhancement

---

Description

• Add GitHub Actions workflow for Cloud Run deployment

• Implement automated deployment using Google's official action

---

Diagram Walkthrough

flowchart LR
  A["GitHub Actions Workflow"] -- "Deploy to Cloud Run" --> B["google-github-actions/deploy-cloudrun@v3"]

Loading

File Walkthrough

	Relevant files
Enhancement	cloudrun.yml Add Cloud Run deployment workflow configuration                    .github/workflows/cloudrun.yml Create new GitHub Actions workflow file Configure Cloud Run deployment step using google-github-actions/deploy-cloudrun@v3 Enable automated deployment pipeline +2/-0

---

Summary by CodeRabbit

• Chores
  • Added Google Cloud Run deployment automation to the GitHub Actions workflow.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
qcx	Building	Preview, Comment	Jan 14, 2026 2:03pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

A new deployment step is added to the Cloud Run GitHub Actions workflow using the deploy-cloudrun action (v3) to automate deployment to Google Cloud Run.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow \.github/workflows/cloudrun\.yml	Added "Deploy to Cloud Run" step using the google-github-actions/deploy-cloudrun@v3 action to automate Cloud Run deployment

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A step so swift, to the cloud it hops,
Google Run awaits, deployment never stops!
GitHub Actions flows, with automation's grace,
Cloud infrastructure now in perfect place! ☁️

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 196583e and 2263baf.

📒 Files selected for processing (1)

• .github/workflows/cloudrun.yml

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Action supply-chain risk Description: The workflow uses a third-party GitHub Action (google-github-actions/deploy-cloudrun@v3) without pinning to an immutable commit SHA, creating a supply-chain risk where a compromised or changed tag could execute unintended code during CI/CD. cloudrun.yml [1-2] Referred Code - name: Deploy to Cloud Run uses: google-github-actions/deploy-cloudrun@v3
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[charliecreates]

The new .github/workflows/cloudrun.yml is currently only a step fragment and lacks required workflow keys (name, on, jobs), so it will not execute in GitHub Actions. It also omits required authentication/configuration typically needed for deploy-cloudrun@v3 (e.g., google-github-actions/auth@v2 and deploy with: inputs).

Summary of changes

Added

• Introduced a new GitHub Actions workflow file at .github/workflows/cloudrun.yml.
• The file currently contains a single step that invokes google-github-actions/deploy-cloudrun@v3 with the step name Deploy to Cloud Run.

[charliecreates]

This file is not a valid GitHub Actions workflow as written. A workflow requires top-level keys like name: and on: (and typically a jobs: block). The current content looks like a step snippet, but it’s placed as the entire workflow file, so GitHub will fail to load/run it.

Suggestion

Replace this with a complete workflow structure (name, on, jobs, steps) and include required auth/config for Cloud Run deploy. For example:

name: Deploy to Cloud Run

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: actions/checkout@v4

      - id: auth
        uses: google-github-actions/auth@v2
        with:
          workload_identity_provider: ${{ secrets.GCP_WIF_PROVIDER }}
          service_account: ${{ secrets.GCP_SERVICE_ACCOUNT }}

      - name: Deploy to Cloud Run
        uses: google-github-actions/deploy-cloudrun@v3
        with:
          service: ${{ secrets.CLOUD_RUN_SERVICE }}
          region: ${{ secrets.GCP_REGION }}
          source: .

Adjust trigger/inputs to match how you deploy (from source, a prebuilt image, etc.). Reply with "@CharlieHelps yes please" if you’d like me to add a commit with this suggestion.

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add required workflow structure Add the required top-level GitHub Actions structure, including name, on trigger, and a jobs section, as the current file is an invalid workflow. .github/workflows/cloudrun.yml [1-2] -- name: Deploy to Cloud Run - uses: google-github-actions/deploy-cloudrun@v3 +name: Cloud Run Deployment +on: + push: + branches: + - main +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Deploy to Cloud Run + uses: google-github-actions/deploy-cloudrun@v3 + with: + project_id: ${{ secrets.GCP_PROJECT }} + service: my-service + image: gcr.io/${{ secrets.GCP_PROJECT }}/my-service + region: us-central1 + Apply / Chat Suggestion importance[1-10]: 9 __ Why: This suggestion correctly identifies that the entire GitHub Actions workflow structure is missing, which makes the file invalid. Providing a complete structure is a critical fix.	High
	Add required deployment parameters Add the mandatory service and region parameters to the deploy-cloudrun action, as their absence will cause the deployment to fail. .github/workflows/cloudrun.yml [1-2] - name: Deploy to Cloud Run uses: google-github-actions/deploy-cloudrun@v3 + with: + service: your-service-name + region: us-central1 + source: ./ Apply / Chat Suggestion importance[1-10]: 8 __ Why: This suggestion correctly identifies that the deploy-cloudrun action is missing mandatory parameters like service and region, which would cause the deployment to fail.	Medium
More