Modify export-ignore entries in .gitattributes

[sasezaki]

Updated export-ignore rules in .gitattributes.

Current archive targets are as follows,

gh api repos/yamadashy/phpstan-friendly-formatter/tarball/HEAD | tar -tzf - | cut -d/ -f2- | sed '/^$/d' | grep -v src/
.devcontainer/
.devcontainer/Dockerfile
.devcontainer/devcontainer.json
.tool-versions
.typos.toml
CLAUDE.md
LICENSE.md
composer.json
docs/
docs/example.png
docs/github-actions.png
extension.neon
phpunit.xml
playground/
playground/dead_code.php
playground/logic_errors.php
playground/missing_types.php
playground/phpstan.neon
playground/type_errors.php
playground/undefined_errors.php

With this PR, The archive targets will be as follows:

gh api repos/sasezaki/phpstan-friendly-formatter/tarball/patch-1 | tar -tzf - | cut -d/ -f2- | sed '/^$/d' | grep -v src
LICENSE.md
composer.json
extension.neon

---

[gemini-code-assist]

Summary of Changes

Hello @sasezaki, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the project's distribution archives by modifying the .gitattributes file. The updated export-ignore rules ensure that only the core, essential files for the phpstan-friendly-formatter extension are included in packaged releases, leading to a cleaner and more focused distribution by excluding development-related assets and configuration files.

Highlights

• Archive Content Reduction: The export-ignore rules in .gitattributes have been updated to significantly reduce the number of files included in distribution archives, focusing solely on essential project components.
• Broadened Exclusion Scope: A new .* export-ignore rule has been added to broadly exclude most dotfiles and dot-directories from archives by default.
• Specific Development Asset Exclusions: Directories like /docs and /playground, along with files such as CLAUDE.md and phpunit.xml, are now explicitly ignored during archive creation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively slims down the distributable package by updating the export-ignore rules in .gitattributes. The use of .* to ignore dotfiles is a good simplification. My review includes a suggestion to improve the overall readability and maintainability of the .gitattributes file by sorting and aligning its entries.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional flags.

[yamadashy]

@sasezaki
Thank you for the report and PR!
I hadn't noticed this.

Looks good, so I'll merge it. Will release soon!