fix: check private field in package.json(#102) #103

watilde · 2016-09-12T18:58:57Z

Fix #102. It should not suggest npm publish if the package.json has private: true.

coveralls · 2016-09-12T19:01:43Z

Coverage increased (+0.1%) to 95.062% when pulling 2d4de35 on watilde:patch/check-private into 1ad772a on conventional-changelog:master.

It should not suggest `npm publish` if the package.json has `private: true`.

coveralls · 2016-09-12T19:08:41Z

Coverage increased (+0.1%) to 95.062% when pulling ee5bf76 on watilde:patch/check-private into 1ad772a on conventional-changelog:master.

nexdrew · 2016-09-12T19:29:59Z

LGTM, thanks @watilde!

fix: check the private field in package.json(conventional-changelog#102)

ee5bf76

It should not suggest `npm publish` if the package.json has `private: true`.

watilde force-pushed the patch/check-private branch from 2d4de35 to ee5bf76 Compare September 12, 2016 19:04

stevemao merged commit 2ce4160 into conventional-changelog:master Sep 12, 2016

watilde deleted the patch/check-private branch September 13, 2016 06:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: check private field in package.json(#102) #103

fix: check private field in package.json(#102) #103

watilde commented Sep 12, 2016

coveralls commented Sep 12, 2016 •

edited

Loading

coveralls commented Sep 12, 2016 •

edited

Loading

nexdrew commented Sep 12, 2016

fix: check private field in package.json(#102) #103

fix: check private field in package.json(#102) #103

Conversation

watilde commented Sep 12, 2016

coveralls commented Sep 12, 2016 • edited Loading

coveralls commented Sep 12, 2016 • edited Loading

nexdrew commented Sep 12, 2016

coveralls commented Sep 12, 2016 •

edited

Loading

coveralls commented Sep 12, 2016 •

edited

Loading