-
-
Notifications
You must be signed in to change notification settings - Fork 614
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(pkg): explicitly include files for release #349
Conversation
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.
Please sign CLA and use commitlint for linting commit messages. You can use git cz
for an interactive commit or use one of these.
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.
Thanks!
@dhruvdutt would you say this is a |
chore |
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.
Heyo, didn't read this. Seems to be another PR for this #354 . Could you do the thing I mentioned there? First one to implement gets a lgtm 😄
Rebased with requested commit style. |
Yeah I just added on the ones @ev1stensberg explicitly mentioned, looking into what else is misc though I'm sure you'll be able to rattle off which you don't want more easily as a maintainer. Do you want Looking again, |
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.
LGTM.
@rgbkrk |
Alright, I've organized the npmignore more like the gitignore. |
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.
Uh! I might not have explained it in the best way.
I meant to clean up or not include things that are already listed in gitignore. For instance, .vscode
is currently mentioned in both npmignore and gitignore but if it's in gitignore then it won't be in version control or on GitHub in the first place hence we don't need to mention it in npmignore.
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Do you publish from a developer laptop or from CI? |
IMO we publish manually. You can see the list of npm publishers here. |
Why not using |
.npmignore
Outdated
|
||
# Miscellany |
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.
Consider revising this
@rgbkrk Thanks for your update. I labeled the Pull Request so reviewers will review it again. @ev1stensberg Please review the new changes. |
Switched this over to using |
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.
LGTM.
Just to follow up, even though we're using
Since a |
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.
Amazing job! Thanks!!
|
Thanks! |
🎉 This PR is included in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What kind of change does this PR introduce?
Build related change
Did you add tests for your changes?
N/A
If relevant, did you update the documentation?
N/A
Summary
When running
flow
in a project that useswebpack-cli
, the latest release is causing flow to choke on a non-validjson
file:Since that file shouldn't be part of the release, I added the
.nyc_output
directory to the npm ignore.Does this PR introduce a breaking change?
Nope.