ci: upload the coverage results once and only based on the latest dependencies

[martin-georgiev]

Summary by CodeRabbit

• Chores
  • Refined the automated testing configuration to leverage the latest dependency versions, enhancing test coverage reporting for PHP 8.4.

[coveralls]

coverage: 92.995%. remained the same
when pulling 30e9d19 on run-test-coverage-only-on-latest
into fa59d6b on main.

[coderabbitai]

Walkthrough

The changes adjust the CI workflow for PHP 8.4 in the repository's configuration file. The matrix strategy is updated with added comments and parameters. Specifically, the doctrine-lexer and doctrine-orm dependencies are now set to use the latest versions for generating coverage reports. There are no modifications to exported or public entities.

Changes

File	Summary
.github/workflows/ci.yml	Updated PHP 8.4 matrix strategy: added comments for clarity and set doctrine-lexer and doctrine-orm parameters to 'latest'.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Pipeline
    participant PHP as PHP 8.4 Job
    participant DM as Dependency Manager

    CI->>PHP: Initiate tests with matrix parameters
    PHP->>DM: Request latest doctrine-lexer & doctrine-orm
    DM-->>PHP: Return latest dependencies
    PHP->>CI: Run tests and generate coverage report

Loading

Poem

I'm a rabbit, hopping with glee,
In the code burrow, a change I see!
PHP 8.4 now runs so light,
Fetching the latest with pure delight.
A joyful sprint in our CI trail—
Hoppin' forward, we set sail! 🐰
Cheers to progress on our coding trail!

---

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

• 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

27-29: Dedicated Coverage Job for PHP 8.4 with Latest Dependencies

The new include entry for PHP 8.4 properly sets doctrine-lexer and doctrine-orm to 'latest' and adds the calculate-code-coverage: true flag. This configuration meets the PR objective by ensuring that the coverage report is generated only for the latest dependency versions.

Suggestion: Although GitHub Actions handles undefined matrix keys gracefully (evaluating them as false in this context), you might consider explicitly setting calculate-code-coverage: false for other matrix combinations (or in a default structure) to improve clarity and ensure robust condition evaluation in the "Upload coverage results" step.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fa59d6b and 30e9d19.

📒 Files selected for processing (1)

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

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: PHP 8.1 + Doctrine ORM 2.14 + Doctrine Lexer latest
• GitHub Check: PHP 8.4 + Doctrine ORM 2.14 + Doctrine Lexer 2.1
• GitHub Check: PHP 8.4 + Doctrine ORM 2.18 + Doctrine Lexer 3.0
• GitHub Check: PHP 8.4 + Doctrine ORM 3.0 + Doctrine Lexer 3.0
• GitHub Check: PHP 8.4 + Doctrine ORM 2.18 + Doctrine Lexer latest
• GitHub Check: PHP 8.3 + Doctrine ORM latest + Doctrine Lexer latest
• GitHub Check: PHP 8.4 + Doctrine ORM latest + Doctrine Lexer 3.0
• GitHub Check: PHP 8.3 + Doctrine ORM 3.0 + Doctrine Lexer 3.0
• GitHub Check: PHP 8.2 + Doctrine ORM latest + Doctrine Lexer latest
• GitHub Check: sloth