add deploy staging

[gkorland]

Summary by CodeRabbit

• Chores
  • Enabled CI runs for the staging branch.
  • Switched Azure deployment to use a branch-derived slot name (main → Production, staging → staging).
  • Replaced hard-coded deployment slot with a dynamic value from the workflow environment.
  • No changes to application functionality or user-facing behavior.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
queryweaver	Building	Preview	Comment	Aug 27, 2025 3:08pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds staging to workflow triggers and introduces a computed SLOT_NAME environment variable based on the Git ref (main → Production, staging → staging). Updates the Azure deploy step to use the dynamic slot name. No other workflow steps are modified.

Changes

Cohort / File(s)	Summary
CI/CD Workflow .github/workflows/main_queryweaver.yml	- Add push trigger for staging branch - Define env.SLOT_NAME from github.ref_name (main→Production, staging→staging) - Use env.SLOT_NAME in Azure Web App deploy step instead of hard-coded value

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant Dev as Developer
    participant GH as GitHub
    participant WF as Actions Workflow
    participant AZ as Azure Web App

    Dev->>GH: Push to main or staging
    GH-->>WF: Trigger workflow (on push)
    rect rgb(245,245,255)
    note over WF: Compute env.SLOT_NAME<br/>main → Production<br/>staging → staging
    WF->>WF: Build & test (unchanged)
    end
    WF->>AZ: Deploy using slot = SLOT_NAME
    AZ-->>WF: Deployment result (success/failure)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump the ground—deploys take wing,
Main says “Production,” staging sings.
A branch decides which slot to choose,
No hard-coded paths to lose.
CI hops with tidy cheer,
Slots aligned, the way is clear. 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d3a69e2 and e76f37c.

📒 Files selected for processing (1)

• .github/workflows/main_queryweaver.yml (3 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch staging-deploy

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None