Skip to content
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

Generate self-.gitignore as part of pkg folder #453

Merged
merged 1 commit into from
Dec 27, 2018

Conversation

RReverser
Copy link
Member

As per discussion with @ashleygwilliams in https://twitter.com/ag_dubs/status/1068173944807727110, pkg should be commonly ignored, and the simplest way to do that is to just generate nested .gitignore inside it ignoring everything (including .gitignore itself).


Make sure these boxes are checked! 📦✅

  • You have the latest version of rustfmt installed and have your
    cloned directory set to nightly
$ rustup override set nightly
$ rustup component add rustfmt-preview --toolchain nightly
  • You ran rustfmt on the code base before submitting
  • You reference which issue is being closed in the PR text

✨✨ 😄 Thanks so much for contributing to wasm-pack! 😄 ✨✨

@ashleygwilliams ashleygwilliams self-requested a review December 18, 2018 21:34
@ashleygwilliams ashleygwilliams added this to the 0.6.0 milestone Dec 18, 2018
@ashleygwilliams
Copy link
Member

@RReverser thanks so much for this and so sorry for the delay in reviewing! could you add a small blurb in the documentation and/or README to explain that this directory is now ignored by default?

we may need to wait on landing this til i implement a way to edit package.json and add js or other assets to the pkg, but i imagine that should be for the release directly after the next one (which is happening this week)

@ashleygwilliams ashleygwilliams added waiting on response needs docs please add docs to this PR labels Dec 18, 2018
Copy link
Member

@ashleygwilliams ashleygwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'll file an issue to document this and make sure it happens before 0.6.0!

@RReverser
Copy link
Member Author

Thanks! Sorry - as mentioned in the other thread, I initially sent this from a different laptop and then with holidays and getting sick didn't get around to finishing this.

@ashleygwilliams
Copy link
Member

it's all good, no worries at all <3 thanks for you efforts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants