do not include tests or bin in git archives

[withinboredom]

Summary by CodeRabbit

• Chores
  • Updated settings to exclude the /bin directory from exported archives.
  • Improved build workflow by refining the composer installation command.

[coderabbitai]

Walkthrough

A .gitattributes file was updated to mark the /bin directory with the export-ignore attribute, excluding it from Git archive exports. Additionally, a GitHub Actions workflow was modified to run composer install --ignore-platform-reqs directly instead of prefixed with dphp. No changes to code or public interfaces were made.

Changes

Cohort / File(s)	Change Summary
Git Attributes Export Ignore .gitattributes	Added export-ignore for the /bin directory to exclude it from Git archive exports.
CI Workflow Update .github/workflows/build-cli.yaml	Changed the composer install command in the performance-test job to run without the dphp prefix.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

In the warren, files abound,
But not all must be zipped and bound!
With a twitch of nose, a hop so spry,
Bins now pass us quietly by.
Composer runs without a hitch,
Smooth and swift, no dphp glitch! 🐇✨

---

📜 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 92882e7 and 8a71ece.

📒 Files selected for processing (1)

• .gitattributes (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .gitattributes

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build-docker
• GitHub Check: Unit Tests - PHP

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch exports

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.28%. Comparing base (dba911f) to head (8a71ece).
⚠️ Report is 1 commits behind head on v2.

Additional details and impacted files

@@             Coverage Diff              @@
##                 v2     #153      +/-   ##
============================================
+ Coverage     46.25%   46.28%   +0.02%     
  Complexity     1250     1250              
============================================
  Files            99       99              
  Lines          3565     3565              
============================================
+ Hits           1649     1650       +1     
+ Misses         1916     1915       -1     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/build-cli.yaml (1)

98-102: Verify Composer availability & add non-interactive flags

Removing the dphp wrapper presumes the runtime-tests image already ships a composer binary on $PATH. If that assumption is wrong the job will fail at runtime.
While touching this line, it is also worth adding the standard non-interactive flags to make the step deterministic and faster in CI:

-          composer install --ignore-platform-reqs
+          composer install --ignore-platform-reqs --no-interaction --no-progress --prefer-dist

Please double-check the image and, if needed, install Composer or revert to dphp composer … to guarantee the same PHP environment as the subsequent dphp exec commands.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b3f07bc and 92882e7.

📒 Files selected for processing (1)

• .github/workflows/build-cli.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build-docker
• GitHub Check: Unit Tests - PHP

[github-actions]

Performance Metrics

test	time (s)	memory usage
perf	16.08	170
Fan out/in	60.05	8