fix: Update export-ignore list in .gitattributes to streamline archive contents.

[terabytesoftw]

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

Summary by CodeRabbit

• Chores
  • Updated packaging configuration so downloadable archives now include files that were previously excluded, improving completeness and parity with the source repository.
  • Only removals of exclusions were made; no new exclusions were added.
  • No changes to runtime behavior or APIs; installations and upgrades are unaffected.
  • This helps users who rely on distributed archives (e.g., via packaged downloads) by providing a more comprehensive set of project assets.

[coderabbitai]

Walkthrough

Removed several export-ignore entries from .gitattributes so that various config, tooling, and test-related files are included in git-archive outputs. No new rules were added; other existing rules remain unchanged.

Changes

Cohort / File(s)	Summary
Git archive inclusion updates ./.gitattributes	Deleted export-ignore rules for: .editorconfig, .phpstan.neon, /c3.php, /codeception.yml, /composer-require-checker.json, /ecs.php, /phpstan.neon*, /rector.php, /tests. Other rules untouched.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix: Add .editorconfig and c3.php to export-ignore list in .gitattributes. #135 — Modifies the same .gitattributes entries but in the opposite direction (adds export-ignore for .editorconfig and c3.php).
• fix: Exclude additional configuration files from archive to streamline exports. #131 — Also adjusts export-ignore entries in .gitattributes, adding rules that this PR removes.

Poem

A nibble of flags from the archive tree,
I twitch my whiskers: “Include them, please!”
Tests and configs hop back in line,
Bundles now ship just fine.
Thump-thump—CI will see,
Every carrot where it ought to be. 🥕🐇

---

📜 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 5af203f and 55e94c0.

📒 Files selected for processing (1)

• .gitattributes (0 hunks)

💤 Files with no reviewable changes (1)

• .gitattributes

✨ Finishing Touches

🧪 Generate unit tests

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

---

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 or @coderabbit 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.