Skip to content

chore: Sync Platform on Pull Requests Only #757

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 9, 2025

Conversation

chewy-zlai
Copy link
Collaborator

@chewy-zlai chewy-zlai commented May 9, 2025

Summary

Run push_to_platform on pull request merge only. Also use default message

Checklist

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

Summary by CodeRabbit

  • Chores
    • Updated workflow to run only after a pull request is merged into the main branch, instead of on every push.
    • Adjusted the commit message behavior for subtree updates to use the default message.

Copy link

coderabbitai bot commented May 9, 2025

Walkthrough

The workflow trigger for .github/workflows/push_to_platform.yaml was changed from running on pushes to main to running only when a pull request targeting main is closed and merged. The git subtree pull step now uses the default commit message.

Changes

File(s) Change Summary
.github/workflows/push_to_platform.yaml Changed workflow trigger to PR closed/merged on main; updated subtree pull to use default commit message.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant Workflow

    Developer->>GitHub: Merge PR into main
    GitHub->>Workflow: Trigger workflow (on PR closed & merged)
    Workflow->>Workflow: Run steps (including git subtree pull)
Loading

Possibly related PRs

Suggested reviewers

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

Poem

When PRs merge and branches close,
The workflow wakes from its repose.
No more on every push to main—
Now only merged PRs sustain.
A subtree pulled, commit message plain,
Automation’s dance, without refrain!
🚀

Tip

⚡️ 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 16th. 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 6fcedb5 and ba29f99.

📒 Files selected for processing (1)
  • .github/workflows/push_to_platform.yaml (2 hunks)
🔇 Additional comments (3)
.github/workflows/push_to_platform.yaml (3)

4-6: Workflow trigger updated correctly
Restricts execution to PRs closed against main.


11-11: Ensure merged PR check
if: github.event.pull_request.merged == true safeguards non-merged closures.


54-54: Confirm default subtree commit message
Dropping --message uses Git's default — verify it aligns with your commit conventions.


🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

@chewy-zlai chewy-zlai merged commit 74f0b86 into main May 9, 2025
4 checks passed
@chewy-zlai chewy-zlai deleted the chewy/sync-to-platform branch May 9, 2025 21:30
chewy-zlai added a commit that referenced this pull request May 15, 2025
## Summary

Run push_to_platform on pull request merge only. Also use default
message


## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated workflow to run only after a pull request is merged into the
main branch, instead of on every push.
- Adjusted the commit message behavior for subtree updates to use the
default message.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai added a commit that referenced this pull request May 15, 2025
## Summary

Run push_to_platform on pull request merge only. Also use default
message


## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated workflow to run only after a pull request is merged into the
main branch, instead of on every push.
- Adjusted the commit message behavior for subtree updates to use the
default message.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai added a commit that referenced this pull request May 16, 2025
## Summary

Run push_to_platform on pull request merge only. Also use default
message


## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated workflow to run only after a pull request is merged into the
main branch, instead of on every push.
- Adjusted the commit message behavior for subtree updates to use the
default message.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants