-
Notifications
You must be signed in to change notification settings - Fork 1k
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(karma): install and configure karma-coverage #349
base: v0.3.2-release
Are you sure you want to change the base?
Conversation
Hi @doon, Thank you for this. However, could you please take a look at our Contributing Guide and update your PR accordingly so that we can merge it? |
done! On Fri, Jan 23, 2015 at 1:17 PM, Merott Movahedi notifications@github.com
|
👍 (though I wish npm wouldn't clobber the |
Could you please rebase this on the latest? We've sorted the list of packages in Nothing has changed. You only need to resolve the conflict with yours. |
@Merott |
It looks like it hasn't been rebased on the latest master. I expect to see only 1 commit (i.e. squash the branch), and the only change to "karma-coverage": "^0.2.7", See this guide: You're going to get a merge conflict when you run the
Just keep your own change: "karma-coverage": "^0.2.7", It might be easier to make a brand new PR, if you prefer. It's highly recommended that you use a feature branch too. Hope that helps, and I'm sorry for the rigid requirements. |
Hey Team, |
No material changes to package.json other than adding karma-coverage, but it was re-ordered by the "npm .. -save-dev" run.