Repository navigation
chore: the tests stay out of what Composer installs - #25
Merged
Merged
Conversation
A house that installs this package received its tests too: as many bytes as the code it runs, and never run there. They are marked out of the archive Composer downloads. Nothing else is: the tools and the workflows of a package can be read by others from that same archive.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A house that installs this package received its tests too: as many
bytes as the code it runs, and never run there. This marks
tests/outof the archive Composer downloads.
Only
tests/is marked. The tools and the workflows of a package can beread by others from that same archive, so they stay.
It changes the archive of the next release; the tags already published
keep theirs. Nothing here needs a release of its own.