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

chore(karma): install and configure karma-coverage #349

Open
wants to merge 2 commits into
base: v0.3.2-release
Choose a base branch
from

Conversation

d00n
Copy link

@d00n d00n commented Jan 23, 2015

No material changes to package.json other than adding karma-coverage, but it was re-ordered by the "npm .. -save-dev" run.

@Merott
Copy link
Contributor

Merott commented Jan 23, 2015

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?

@d00n d00n changed the title add and configure karam-coverage, exclude spec files from coverage stats chore(karma): install and configure karam-coverage Jan 23, 2015
@d00n d00n changed the title chore(karma): install and configure karam-coverage chore(karma): install and configure karma-coverage Jan 23, 2015
@d00n
Copy link
Author

d00n commented Jan 23, 2015

done!

On Fri, Jan 23, 2015 at 1:17 PM, Merott Movahedi notifications@github.com
wrote:

Hi @doon https://github.com/doon,

Thank you for this. However, could you please take a look at our Contributing
Guide https://github.com/ngbp/ngbp/blob/v0.3.2-release/CONTRIBUTING.md
and update your PR accordingly so that we can merge it?


Reply to this email directly or view it on GitHub
#349 (comment).

@joshdmiller
Copy link
Member

👍

(though I wish npm wouldn't clobber the package.json every time we added something)

@Merott
Copy link
Contributor

Merott commented Feb 1, 2015

@d00n

Could you please rebase this on the latest? We've sorted the list of packages in package.json to avoid issues with npm messing up the dependencies list.

Nothing has changed. You only need to resolve the conflict with yours.

@d00n
Copy link
Author

d00n commented Feb 11, 2015

@Merott
Done! However, this being my very first rebase , please advise if I borked it.
tx!

@Merott
Copy link
Contributor

Merott commented Feb 11, 2015

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 package.json to be the addition of this line:

"karma-coverage": "^0.2.7",

See this guide:
https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request

You're going to get a merge conflict when you run the rebase command, at which point you're going to need to open package.json in an editor, and look for the conflicting line:

<<<<<<< HEAD
    "karma-coverage": "^0.2.7",
=======
>>>>>>> 268901b9ee08103dd1e9ff2a136b1e46ccb78332

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.

@adamjaffeback
Copy link

Hey Team,
Just recreated and submitted this PR as #374, because I felt that it was important...and relatively simple. Take a look and let me know if I should make any changes.

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.

None yet

4 participants