ci: Update pr-check.yml

[oliursahin]

What does this Pr do?

Fixes:

• [ ] #XXX (GitHub issue number)
• [ ] MAR-XXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Mandatory Tasks:

• I have self-reviewed the code (A decent size PR without self-review might be rejected)
• I pinky swear that my codes gonna work as I have testing every possible scenario.
• I ignored Coderabbit suggestion because it does not make any sense.
• I took Coderabbit suggestion under consideration as some of it makes sense.

How should this be tested?

Environment Setup: ( if applicable)

• Required env variables:

  # Add required env variables here
  

Checklist:

• My code follows the style guidelines of this project.
• I have commented my code, particularly in hard-to-understand areas.
• I have checked if my changes generate no new warnings.
• I have checked for Build errors.
• I have checked if my branch is up to date with preview.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request updates the GitHub Actions workflow configuration in .github/workflows/pr-check.yml to include a new trigger for push events specifically on the preview branch. This allows the workflow to run on direct pushes in addition to pull request events. The job build-and-check remains unchanged in its execution environment and conditions, but it includes steps for synchronizing the current branch with the preview branch.

Changes

File	Change Summary
.github/workflows/pr-check.yml	Added a trigger for push events on the preview branch to the workflow configuration.

Possibly related PRs

• fixes MAR-280 #440: This PR introduces a GitHub Actions workflow that checks if a pull request branch is up-to-date with the preview branch, which is directly related to the changes made in the main PR that also updates the workflow for push events on the preview branch.

Suggested reviewers

• sajdakabir

🐰 In the meadow, a change did bloom,
A push to preview, dispelling gloom.
With workflows dancing, they now align,
Pull requests and pushes, all in good time.
Hops of joy, as builds take flight,
In our rabbit warren, all feels right! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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

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