Create .gitattributes #269
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR adds a .gitattributes file to exclude specific files and directories from exports/installing composer package.
Purpose:
Keeps repository metadata and tooling files out of distribution packages.
Follows best practices for cleaner project exports.
Impact:
No runtime changes—this only affects repository operations like git archive.
deluxetom
approved these changes
Apr 29, 2025
|
Thanks for this, and for the review! |
|
Waiting for tag 2.5.1 to be announced for composer |
|
Are you OK waiting a week or so, or do you need 2.5.1 sooner? libvips 8.17 is due very soon, so it might be better to wait for that. |
|
I am OK, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a .gitattributes file to exclude specific files and directories from exports/installing composer package.
Purpose:
Keeps repository metadata and tooling files out of distribution packages.
Follows best practices for cleaner project exports.
Impact:
No runtime changes — this only affects repository operations like git archive.