We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is quite a bunch of useless files that end up in production servers and workstations. Please add a .gitattributes file, example: https://github.com/code-lts/doctum/blob/main/.gitattributes
.gitattributes
bash-5.1# tree vendor/eluceo/ vendor/eluceo/ └── ical ├── Dockerfile ├── LICENSE ├── Makefile ├── composer.json ├── composer.lock ├── couscous.yml ├── dangerfile.js ├── infection.json ├── package.json ├── rulesets.xml ├── src (removed childs in this tree) └── yarn.lock 14 directories, 73 files
The text was updated successfully, but these errors were encountered:
Is it better to use .gitattributes or composer's archive.exclude here?
archive.exclude
Or both?
Sorry, something went wrong.
Is it better to use .gitattributes or composer's archive.exclude here? Or both?
For having used both previous I would really recommend gitattributes This will reflect on the git archive command
git archive
Done in #510 Only infection.json is left
infection.json
No branches or pull requests
There is quite a bunch of useless files that end up in production servers and workstations.
Please add a
.gitattributes
file, example: https://github.com/code-lts/doctum/blob/main/.gitattributesThe text was updated successfully, but these errors were encountered: