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

Fixing npm install on Windows #22

Closed
wants to merge 11 commits into from
Closed

Conversation

NQNStudios
Copy link
Collaborator

I don't know why 11 commits that it seemed like you already merged in are listed here, but apparently they don't change anything? Idk, pull requests, yikes

@invicticide
Copy link
Owner

invicticide commented Nov 7, 2017

I think the problem here is you're creating a pull request on your fork's dev branch which includes all your prior commits. You'd get a cleaner pull request if you checked out a new branch at the base commit (i.e. the last one on origin before you forked), then committed this fix onto that branch, then issued a pull request for that branch.

Basically, working with a "feature branch" mentality is your friend. ;)

@NQNStudios
Copy link
Collaborator Author

I think I understand what happened. I was also confused about my first pull request which I intended only to include the simple UTF-8 fix but actually included all the Compiler.ts changes.

@invicticide
Copy link
Owner

This got fixed separately at 69a7e72

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

Successfully merging this pull request may close these issues.

2 participants