Skip to content

[CI] Update branches for full builds + refactor and upmerge actions#17887

Merged
TheMilek merged 3 commits intoSylius:2.1from
GSadee:ci-update-full-builds
Apr 22, 2025
Merged

[CI] Update branches for full builds + refactor and upmerge actions#17887
TheMilek merged 3 commits intoSylius:2.1from
GSadee:ci-update-full-builds

Conversation

@GSadee
Copy link
Copy Markdown
Member

@GSadee GSadee commented Apr 22, 2025

Q A
Branch? 2.1
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Related tickets
License MIT

Summary by CodeRabbit

  • Chores
    • Updated scheduled run times for continuous integration workflows to new daily time slots.
    • Updated workflow configurations and labels to reference version 2.1 instead of 1.13.
    • Adjusted coding standard checks to run on updated branches and PHP versions.
    • Updated documentation links in automated pull requests to reference the latest workflow files.

@GSadee GSadee added the CI label Apr 22, 2025
@GSadee GSadee requested review from a team as code owners April 22, 2025 11:51
@probot-autolabeler probot-autolabeler bot added the Maintenance CI configurations, READMEs, releases, etc. label Apr 22, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 22, 2025

Walkthrough

The changes update several GitHub Actions workflow files to adjust scheduled run times, update branch and version references, and modify job matrices. Specifically, the scheduled times for multiple CI workflows were shifted to earlier or later times, branch references were updated from older versions (such as 1.13) to newer ones (such as 2.1), and documentation links in workflow-generated pull requests were revised to point to the correct workflow files for the new branch versions. No changes were made to workflow logic or exported entities.

Changes

File(s) Change Summary
.github/workflows/ci__full_1_14.yaml Changed CI workflow schedule from 2:00 AM to 1:00 AM daily.
.github/workflows/ci__full_2_0.yaml Changed CI workflow schedule from 3:00 AM to 2:00 AM daily.
.github/workflows/ci__full_2_1.yaml Updated workflow to reference version 2.1 instead of 1.13; changed schedule to 3:00 AM; updated concurrency and job matrices to use 2.1.
.github/workflows/refactor.yaml Replaced branch 1.13/PHP 8.1 matrix entry with 2.1/PHP 8.2; updated PR body text to reference 2.1 branch.
.github/workflows/upmerge_pr.yaml Updated PR body documentation link from 1.13 branch to 2.1 branch.

Sequence Diagram(s)

sequenceDiagram
    participant Scheduler
    participant GitHub Actions Workflow

    Scheduler->>GitHub Actions Workflow: Trigger workflow at scheduled time (per updated cron)
    GitHub Actions Workflow->>GitHub Actions Workflow: Run jobs for specified branch/version
    GitHub Actions Workflow-->>Scheduler: Report status/results
Loading

Poem

In the warren where workflows hop in the night,
Schedules shift softly, new versions in sight.
Branches now fresher, with numbers anew,
Refactors and merges, all hopping right through.
With a twitch of the nose and a thump of the paw,
The CI runs earlier—hip hip hurrah!
🐇✨


📜 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 18d181c and b13e10f.

📒 Files selected for processing (2)
  • .github/workflows/ci__full_1_14.yaml (1 hunks)
  • .github/workflows/ci__full_2_0.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • .github/workflows/ci__full_2_0.yaml
  • .github/workflows/ci__full_1_14.yaml

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
🪧 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 generate docstrings to generate docstrings for 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.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/ci__full_2_0.yaml (1)

6-6: Approve schedule update and concurrency alignment, but update inline comment.
The cron expression correctly shifts the run to 2:00 AM, aligning with the branch’s CI window. However, the inline comment still reads “Run every day at 3am”, which is now inaccurate.

Consider updating the comment to:

cron: "0 2 * * *" # Run every day at 2am
.github/workflows/ci__full_1_14.yaml (1)

6-6: Approve schedule change, but correct the inline comment time.
The cron schedule has been updated to “0 1 * * *” (1 AM), matching the intended CI timing. The existing comment “Run every day at 2am” is now outdated.

Please update the comment to:

cron: "0 1 * * *" # Run every day at 1am
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9c05447 and 18d181c.

📒 Files selected for processing (5)
  • .github/workflows/ci__full_1_14.yaml (1 hunks)
  • .github/workflows/ci__full_2_0.yaml (1 hunks)
  • .github/workflows/ci__full_2_1.yaml (6 hunks)
  • .github/workflows/refactor.yaml (2 hunks)
  • .github/workflows/upmerge_pr.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (14)
  • GitHub Check: End-to-end tests (MySQL) / Non-JS, PHP 8.3, Symfony ^7.2 (test_cached), MySQL 8.4, Twig ^3.3
  • GitHub Check: End-to-end tests (MySQL) / JS with Chromedriver, PHP 8.3, Symfony ^7.2 (test_cached), MySQL 8.4, Twig ^3.3
  • GitHub Check: End-to-end tests (MySQL) / JS with Panther, PHP 8.3, Symfony ^7.2 (test_cached), MySQL 8.4, Twig ^3.3
  • GitHub Check: End-to-end tests (MySQL) / Non-JS, PHP 8.2, Symfony ^6.4 (test_cached), MySQL 8.0, Twig ^3.3
  • GitHub Check: End-to-end tests (MySQL) / JS with Chromedriver, PHP 8.2, Symfony ^6.4 (test_cached), MySQL 8.0, Twig ^3.3
  • GitHub Check: End-to-end tests (MySQL) / JS with Panther, PHP 8.2, Symfony ^6.4 (test_cached), MySQL 8.0, Twig ^3.3
  • GitHub Check: End-to-end tests (PostgreSQL) / Non-JS, PHP 8.3, Symfony ^7.2, PostgreSQL 16.4
  • GitHub Check: End-to-end tests (PostgreSQL) / Non-JS, PHP 8.2, Symfony ^6.4, PostgreSQL 15.8
  • GitHub Check: Frontend / NodeJS 20.x
  • GitHub Check: Packages / PHP 8.3, Symfony ^7.2
  • GitHub Check: Packages / PHP 8.2, Symfony ^6.4
  • GitHub Check: End-to-end tests (MariaDB) / Non-JS, PHP 8.3, Symfony ^7.2, MariaDB 11.4.3, State Machine Adapter winzou_state_machine
  • GitHub Check: End-to-end tests (MariaDB) / Non-JS, PHP 8.3, Symfony ^7.2, MariaDB 11.4.3, State Machine Adapter symfony_workflow
  • GitHub Check: End-to-end tests (MariaDB) / Non-JS, PHP 8.2, Symfony ^6.4, MariaDB 10.11.9, State Machine Adapter symfony_workflow
🔇 Additional comments (7)
.github/workflows/upmerge_pr.yaml (1)

59-59: Approve PR body link update to reflect the new 2.1 branch.
The documentation link in the pull request body now correctly points to the upmerge_pr.yaml workflow in the 2.1 branch. This change ensures users access the right version of the workflow file.

.github/workflows/ci__full_2_1.yaml (4)

1-1: Approve workflow name update.
The workflow name has been updated from “Continuous Integration 1.13 (Full)” to “Continuous Integration 2.1 (Full)”, accurately reflecting the new branch version for the full CI pipeline.


6-6: Approve cron schedule change.
The cron expression has been updated to run at 3:00 AM (0 3 * * *), matching the desired schedule for branch 2.1.


10-11: Approve concurrency group identifier update.
The concurrency group now includes 2_1-full, ensuring that only one full CI run per branch 2.1 is active at a time.


20-21: Approve branch matrix updates across jobs.
All job matrices have been updated to target branch 2.1, ensuring consistency across static checks, end-to-end tests, and package workflows.

Also applies to: 29-30, 39-40, 49-50, 66-67

.github/workflows/refactor.yaml (2)

33-36: Approve addition of branch 2.1 in the matrix.
The matrix now includes a 2.1 entry with PHP 8.2, aligning the coding-standard workflow with the new branch and PHP version strategy.


66-66: Approve PR body link update for refactor workflow.
The pull request description now correctly references refactor.yaml in the 2.1 branch, ensuring accurate documentation.

TheMilek
TheMilek previously approved these changes Apr 22, 2025
mpysiak
mpysiak previously approved these changes Apr 22, 2025
@GSadee GSadee dismissed stale reviews from mpysiak and TheMilek via b13e10f April 22, 2025 11:57
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 22, 2025

✅ Preview Environment deployed on Bunnyshell

Component Endpoints
mailhog https://mailhog-lf47kq.bunnyenv.com/
php https://store-lf47kq.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands:

  • 🔴 /bns:stop to stop the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

@TheMilek TheMilek merged commit 71e7a37 into Sylius:2.1 Apr 22, 2025
27 checks passed
@GSadee GSadee deleted the ci-update-full-builds branch April 22, 2025 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Maintenance CI configurations, READMEs, releases, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants