Skip to content

[TASK] Restructure build files and switch to reusable workflows#82

Merged
eliashaeussler merged 1 commit into
mainfrom
task/restructure
Jun 18, 2026
Merged

[TASK] Restructure build files and switch to reusable workflows#82
eliashaeussler merged 1 commit into
mainfrom
task/restructure

Conversation

@eliashaeussler

Copy link
Copy Markdown
Owner

No description provided.

@eliashaeussler eliashaeussler added the maintenance Code base is being maintained label Jun 18, 2026
@eliashaeussler eliashaeussler self-assigned this Jun 18, 2026
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@eliashaeussler, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 minutes and 31 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 55564db7-ff35-44cb-b534-d83d081253c7

📥 Commits

Reviewing files that changed from the base of the PR and between effa250 and f546548.

⛔ Files ignored due to path filters (1)
  • composer.lock is excluded by !**/*.lock
📒 Files selected for processing (15)
  • .gitattributes
  • .github/settings.yml
  • .github/workflows/cgl.yaml
  • .github/workflows/ci.yaml
  • .github/workflows/release.yaml
  • .github/workflows/tests.yaml
  • .gitignore
  • CONTRIBUTING.md
  • README.md
  • build/checks/.php-cs-fixer.php
  • build/checks/phpstan.php
  • build/checks/rector.php
  • build/tests/.gitignore
  • build/tests/phpunit.xml
  • composer.json

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@eliashaeussler eliashaeussler merged commit d4dca40 into main Jun 18, 2026
20 checks passed
@eliashaeussler eliashaeussler deleted the task/restructure branch June 18, 2026 19:08
@coveralls

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 27782957063

Coverage remained the same at 86.31%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 168
Covered Lines: 145
Line Coverage: 86.31%
Coverage Strength: 4.39 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Code base is being maintained

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants