fix: Update .gitattributes to exclude additional files from the package.

[terabytesoftw]

Q	A
Is bugfix?	✔️
New feature?	❌
Breaks BC?	❌

Summary by CodeRabbit

• Chores
  • Updated packaging configuration to exclude non-essential development and configuration assets from release archives, resulting in smaller downloads and cleaner distributions.
  • Improves installation speed and reduces clutter in published packages.
  • No changes to application behavior, interfaces, or public APIs.

[coderabbitai]

Walkthrough

Adds export-ignore entries to .gitattributes for five files to exclude them from generated archives. No code or API changes.

Changes

Cohort / File(s)	Summary
Packaging metadata ./.gitattributes	Added export-ignore for .editorconfig, ecs.php, infection.json5, phpstan.neon, and runtime; existing entries unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

bug

Poem

A nibble of bytes, a tweak to the crate,
I boxed up the repo to trim down the freight.
Hoppity-hop, archives now light,
Dev tools stay home, the package feels right.
Carrot-sharp curation—ship it tonight! 🥕✨

---

📜 Recent review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between eceef54 and 03fb7da.

📒 Files selected for processing (1)

• .gitattributes (1 hunks)

🔇 Additional comments (2)

.gitattributes (2)

29-29: Solid packaging hygiene: excluding dev-only/config files is appropriate

Excluding .editorconfig, ecs.php, infection.json5, phpstan.neon, and the runtime directory from archives reduces package size and avoids shipping non-runtime tooling/config. No BC impact and aligns with Composer’s export-ignore behavior.

Also applies to: 37-39, 43-43

---

29-29: Archive exclusions verified

Ran the provided archive‐verification script against HEAD; no excluded files were found in the generated archive. Exclusions are working as intended.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-mini-41

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.