-
Notifications
You must be signed in to change notification settings - Fork 266
Ship .gitattributes
file to shrink the dist package
#1020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This is considered a best practice AFAIK
bb7d4c2
to
440ad22
Compare
tests export-ignore | ||
docs export-ignore | ||
examples export-ignore | ||
mongo-orchestration export-ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This directory hasn't been updated in over two years and I think it's obsolete since stopped using Travis CI and migrated to GitHub Actions (including the mongo-orchestration action in drivers-evergreen-tools). I also found no references to this directory in the project.
@alcaeus: Do you concur that we should remove it entirely?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened PHPLIB-1058 to track this.
examples export-ignore | ||
mongo-orchestration export-ignore | ||
tools export-ignore | ||
Makefile export-ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file might just be a candidate for removal, per #1021 (comment).
docs export-ignore | ||
examples export-ignore | ||
mongo-orchestration export-ignore | ||
tools export-ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to include examples/
and tests/
in exports since they're intended for our users. @alcaeus: thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to refer to the documentation in this case. If someone really needs this, one can hop over to github or use prefer source composer option.
We save a lot of traffic when thinking about CI ✌🏻
It's up to you 🤓
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm admittedly in the minority of users that frequently jumps through the vendor/
directory to reference code. The impact on CI and users specifying --prefer-source
are both good points. I'm on board with stripping all of this from the git archive in that case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is good to merge as-is. The mongo-orchestration
and Makefile
lines can be addressed later in separate PRs as needed.
I will open PRs when back from vacation 👍 |
This is considered a best practice AFAIK