fix: Reenable platform sync

[chewy-zlai]

Summary

This removes the check for platform sync to only happen on pull requests. This check blocked runs now that we are using main-passing-tests

Checklist

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

Summary by CodeRabbit

• Chores
  • Updated workflow so that certain automated tasks now run on every push to the main-passing-tests branch, rather than only after pull requests are merged. No changes to user-facing features.

[coderabbitai]

Walkthrough

The workflow .github/workflows/push_to_platform.yaml was updated by removing the condition that limited the subtree-pull job to only run after merged pull requests. Now, the job executes on every push to the main-passing-tests branch.

Changes

File(s)	Change Summary
.github/workflows/push_to_platform.yaml	Removed conditional execution (if: github.event.pull_request.merged == true) from the subtree-pull job, so it now runs on every push to main-passing-tests. No other workflow steps were altered.

Possibly related PRs

• chore: Sync Workflow Use main-passing-tests #804: Also modifies the push_to_platform.yaml workflow to change triggers and branch references, indicating related workflow configuration changes.
• chore: Sync Platform on Pull Requests Only #757: Previously added the conditional execution now being removed, directly affecting the same job and workflow logic.
• fix: Sync Workflow Lives in Chronon #743: Alters the same workflow file, focusing on replacing reusable workflows with inline sync logic, thus related to workflow execution mechanics.

Suggested reviewers

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

Poem

On every push, the job will run,
No longer waits for PRs done.
The workflow’s gate is open wide,
Each commit takes a platform ride.
With triggers clear and checks anew,
Automation marches through! 🚀

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.

---

📜 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 7e9e610 and a1b63ed.

📒 Files selected for processing (1)

• .github/workflows/push_to_platform.yaml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/push_to_platform.yaml

---

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