Add Makefile to export-ignore in .gitattributes #56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Makefile to export-ignore in .gitattributes
This PR adds the Makefile to the export-ignore list in .gitattributes to prevent it from being included in distribution packages.
Motivation and Context
The Makefile contains development-specific commands and shortcuts that are only useful for contributors working on the codebase. End users who install this package via Composer don't need the Makefile in their vendor directory, as it's purely a development tool. Adding it to export-ignore reduces the package size and keeps the distributed package clean by excluding development-only files.
How Has This Been Tested?
This change affects only the package distribution and doesn't impact runtime functionality. The change can be verified by:
Breaking Changes
No breaking changes. This only affects package distribution and has no impact on the API or functionality.
Types of changes
Checklist
Additional context
This follows the existing pattern in .gitattributes where other development files like .php-cs-fixer.dist.php, phpstan.dist.neon, and phpunit.xml.dist are already excluded from exports. The Makefile contains common development tasks like running tests, code style fixes, and static analysis, which are only relevant for contributors.