Update CI

[alistair3149]

• Use experimental flags like the other CIs
• Add PHP 8.4 and master
• Use PHP 8.3 for MW 1.43

Summary by CodeRabbit

• Chores
  • Enhanced our automated testing process with refined error handling and additional test configurations for improved stability.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update the CI workflow configuration by introducing an experimental parameter in the job matrix. The new parameter controls the behavior of the continue-on-error directive for the test job. Additionally, a new matrix entry with mw: 'master', php: 8.4, and experimental: true is added, while existing matrix entries now explicitly set experimental: false.

Changes

File	Change Summary
.github/workflows/ci.yml	Introduced the experimental parameter in the job matrix; updated the continue-on-error directive to depend on this parameter; added a new matrix entry (mw: 'master', php: 8.4, experimental: true); updated existing entries to include experimental: false.

---

📜 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 34cef0f and 051aa03.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (1 hunks)

🔇 Additional comments (3)

.github/workflows/ci.yml (3)

12-12: Dynamic Control of Job Failure Behavior

Using ${{ matrix.experimental }} for continue-on-error cleanly parameterizes whether a job should fail or continue on error based on its experimental status. This approach enhances flexibility and aligns perfectly with the PR objectives.

---

17-43: Explicit Experimental Flag on Existing Matrix Entries

Each existing matrix entry now explicitly includes experimental: false. This not only improves the clarity of the configuration but also ensures that all non-experimental CI jobs behave consistently.

---

44-46: Addition of Experimental Matrix Entry for Master Branch

The new matrix entry for mw: 'master' with php: 8.4 and experimental: true is a well-considered inclusion. It introduces experimental testing on the master branch using PHP 8.4 while allowing the CI to continue on error, which is ideal for early detection without blocking the pipeline. Please verify that this experimental behavior is thoroughly documented and that any downstream steps handle potential failures gracefully.

---

🪧 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. (Beta)
• @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.