Fix documentation links

[msmakouz]

Q	A
Bugfix?	❌
Breaks BC?	❌
New feature?	❌

• Need to fix tests
• Need to fix Psalm issues

Summary by CodeRabbit

• Chores
  • Updated workflow triggering conditions and PHP version preferences for better compatibility and performance.
  • Enhanced static analysis workflow by removing branch restrictions and updating PHP version settings.

[coderabbitai]

Walkthrough

The modifications involve refining the automation of testing and static analysis for a PHP project. Specifically, these updates broaden the conditions under which automated workflows are triggered and fine-tune the PHP environment settings. This ensures a more inclusive and up-to-date checking process, enhancing the project's code quality and compatibility across different PHP versions.

Changes

File Path	Change Summary
.github/workflows/...	Modified triggering conditions, updated PHP versions and stability preferences in phpunit.yml
.github/workflows/...	Removed master branch restriction for push events, adjusted PHP version in psalm.yml

🐰✨
In the realm of code where the green tests run,
A rabbit tweaked workflows, hopping in fun.
"Let's broaden our checks," it said with a smile,
For PHP versions and branches, across every mile.
Now every push and pull, in harmony they sing,
Ensuring the code's quality, in this digital spring.
🌼🐰

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.93%. Comparing base (1a25f03) to head (2b20bed).

Additional details and impacted files

@@            Coverage Diff            @@
##                2.x      #10   +/-   ##
=========================================
  Coverage     78.93%   78.93%           
  Complexity      147      147           
=========================================
  Files            23       23           
  Lines           489      489           
=========================================
  Hits            386      386           
  Misses          103      103           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 1a25f03 and 2b20bed.

Files ignored due to path filters (1)

• composer.json is excluded by: !**/*.json

Files selected for processing (2)

• .github/workflows/phpunit.yml (2 hunks)
• .github/workflows/psalm.yml (2 hunks)

Additional comments: 4

.github/workflows/psalm.yml (2)

• 5-6: Removing the master branch restriction for push events is a good practice, as it allows for more comprehensive CI across different branches.
• 5-6: Please verify the PHP version used by the workflow after the removal of explicit PHP version configuration. Consider re-adding the PHP version configuration to ensure the workflow runs with the intended PHP version.

.github/workflows/phpunit.yml (2)

• 5-6: Removing the master branch restriction for push events in the PHPUnit workflow aligns with good CI practices, similar to the changes in the Psalm workflow.
• 12-13: Adding stability preferences (['prefer-lowest', 'prefer-stable']) is a commendable practice for ensuring compatibility across different dependency versions. Ensure that the PHP versions used for testing are explicitly defined if necessary.