chore: Sync Workflow Use main-passing-tests

[chewy-zlai]

Summary

Use main-passing-tests to update platform instead of main.
Slack notification if merge to main-passing-tests fails.
Use deploy key for merging to main-passing-tests so we can lock down pushes to it.

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• Chores
  • Updated workflow authentication for improved security during branch checkouts.
  • Adjusted workflow triggers and dependencies to ensure jobs run in the correct order and respond to the appropriate branch events.

[coderabbitai]

Walkthrough

The workflows for pushing to canary and platform branches were updated. The canary workflow now uses an SSH key for branch checkout and adjusts job dependencies for failure notifications. The platform workflow trigger and subtree pull branch were changed from main to main-passing-tests.

Changes

File(s)	Change Summary
.github/workflows/push_to_canary.yaml	Added SSH key to checkout step and updated on_fail_notify_slack job dependencies to include merge job.
.github/workflows/push_to_platform.yaml	Changed workflow trigger to main-passing-tests pushes and updated subtree pull to use main-passing-tests.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Repo
    participant Slack

    GitHub Actions->>Repo: Checkout main branch (with SSH key)
    GitHub Actions->>GitHub Actions: Run merge_to_main-passing-tests job
    GitHub Actions->>GitHub Actions: Run integration tests (AWS/GCP)
    alt Any job fails
        GitHub Actions->>Slack: Notify on failure
    end

Loading

Possibly related PRs

• chore: Sync Platform on Pull Requests Only #757: Also modifies .github/workflows/push_to_platform.yaml, changing triggers and branch logic.
• fix: Sync Workflow Lives in Chronon #743: Alters or deletes push_to_canary.yaml, directly related to the workflow updated here.
• Revive push_to_canary #754: Introduces or modifies push_to_canary.yaml, which is further updated in this PR.

Suggested reviewers

• kumar-zlai
• david-zlai
• tchow-zlai

Poem

Workflows shift and branches sway,
SSH keys unlock the way.
Canary and platform, in sync anew,
Triggers change—jobs march through.
With each commit, the pipelines cheer,
CI/CD magic drawing near!
🚀

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a48b1a6 and a70e25f.

📒 Files selected for processing (2)

• .github/workflows/push_to_canary.yaml (2 hunks)
• .github/workflows/push_to_platform.yaml (2 hunks)

🔇 Additional comments (4)

.github/workflows/push_to_platform.yaml (2)

4-6: Trigger updated main-passing-tests branch will now kick off this workflow.

---

52-54: Sync branch Subtree pull now uses main-passing-tests.

.github/workflows/push_to_canary.yaml (2)

496-500: Auth Checkout now uses SSH key for merge step. Ensure ${{ secrets.CHRONON_REPO_DEPLOY_KEY }} is configured.

---

528-529: Slack notify Added merge_to_main-passing-tests to failure deps. Looks correct.

---

🪧 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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• 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.