Skip to content

Conversation

@GautierDele
Copy link
Member

@GautierDele GautierDele commented Jun 25, 2025

Summary by CodeRabbit

  • Chores
    • Updated repository settings to exclude certain files and directories from archive exports, resulting in cleaner downloads for end-users.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 25, 2025

Walkthrough

A new .gitattributes file has been added to the repository. This file configures certain files and directories—including configuration files, test files, and GitHub-specific directories—to be excluded from archive exports by applying the export-ignore attribute.

Changes

File(s) Change Summary
.gitattributes Added to define export-ignore rules for specific files/dirs

Poem

In the warren, files hop and hide,
Some now vanish when archives are supplied.
Tests and configs take a nap,
While exports travel light on the map.
With .gitattributes set just right,
Our bundles hop off, feather-light!
🐇📦✨


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
🪧 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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.gitattributes (1)

1-6: Optional: widen coverage for other dev-only files

If the repository also contains static-analysis or tooling configs (e.g. phpstan.neon*, ecs.php, .php-cs-fixer.php, docker-compose*, etc.) you could add them to the list to keep release archives even leaner:

+/phpstan*.neon        export-ignore
+/ecs.php              export-ignore
+/.php-cs-fixer.php    export-ignore
+/docker-compose*      export-ignore

Ignore if none of these files exist.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2510705 and 36ed260.

📒 Files selected for processing (1)
  • .gitattributes (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (18)
  • GitHub Check: Tests on PHP 8.4 with Laravel ^12.0 and pgsql
  • GitHub Check: Tests on PHP 8.4 with Laravel ^11.0 and pgsql
  • GitHub Check: Tests on PHP 8.4 with Laravel ^12.0 and sqlite
  • GitHub Check: Tests on PHP 8.3 with Laravel ^12.0 and pgsql
  • GitHub Check: Tests on PHP 8.3 with Laravel ^12.0 and mysql
  • GitHub Check: Tests on PHP 8.4 with Laravel ^11.0 and sqlite
  • GitHub Check: Tests on PHP 8.2 with Laravel ^12.0 and pgsql
  • GitHub Check: Tests on PHP 8.4 with Laravel ^12.0 and mysql
  • GitHub Check: Tests on PHP 8.4 with Laravel ^11.0 and mysql
  • GitHub Check: Tests on PHP 8.2 with Laravel ^12.0 and mysql
  • GitHub Check: Tests on PHP 8.3 with Laravel ^11.0 and pgsql
  • GitHub Check: Tests on PHP 8.3 with Laravel ^12.0 and sqlite
  • GitHub Check: Tests on PHP 8.2 with Laravel ^11.0 and mysql
  • GitHub Check: Tests on PHP 8.3 with Laravel ^11.0 and mysql
  • GitHub Check: Tests on PHP 8.3 with Laravel ^11.0 and sqlite
  • GitHub Check: Tests on PHP 8.2 with Laravel ^11.0 and pgsql
  • GitHub Check: Tests on PHP 8.2 with Laravel ^11.0 and sqlite
  • GitHub Check: Tests on PHP 8.2 with Laravel ^12.0 and sqlite
🔇 Additional comments (1)
.gitattributes (1)

1-6: Entries look correct – no functional issues identified

The patterns will exclude the intended development / CI artefacts from git archive output.
Nice housekeeping. 👍

@GautierDele GautierDele merged commit a48d5ab into main Jun 25, 2025
21 checks passed
@GautierDele GautierDele deleted the feature/remove-unused-files-in-compilation branch June 25, 2025 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants