-
Notifications
You must be signed in to change notification settings - Fork 20
chore: improve .npmignore #2243
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
chore: improve .npmignore #2243
Conversation
Signed-off-by: Zhan Milenkov <[email protected]>
E2E Test Report 19 files 134 suites 1h 52m 20s ⏱️ Results for commit 0c9330c. ♻️ This comment has been updated with latest results. |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesFootnotes
|
…ee-what-npm-is-installing-with-solo-and-perhaps-there-is-more-to-add-to-npmignore
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…ee-what-npm-is-installing-with-solo-and-perhaps-there-is-more-to-add-to-npmignore
🎉 This PR is included in version 0.40.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Related Issues
Pull request (PR) checklist
package.json
changes have been explained to and approved by a repository managerTesting
The following manual testing was done:
The following was not tested:
Commit message guidelines
We use 'Conventional Commits' to ensure that our commit messages are easy to read, follow a consistent format, and for automated release note generation. Please follow the guidelines below when writing your commit messages: