eslint-plugin-modules-newline icon indicating copy to clipboard operation
eslint-plugin-modules-newline copied to clipboard

Published 20 hours ago • verified publisher icon gmsorrow

continuous integration

Open oprogramador opened this issue 4 years ago • 4 comments

Could you add a CI so we could easily see whether the tests are passing and whether the code from this repo (but not any other code which maybe is missing in this repo) is published to NPM?

oprogramador avatar Mar 25 '21 20:03 oprogramador

@oprogramador CI tests are setup. Please feel free to add NPM publish to Circle CI config.

gmsorrow avatar Mar 31 '21 21:03 gmsorrow

@gmsorrow

Can I also add semantic-release which not only publishes to NPM but also bumps NPM versions (with pushing to GitHub)?

oprogramador avatar Apr 03 '21 21:04 oprogramador

@gmsorrow

Can I also add semantic-release which not only publishes to NPM but also bumps NPM versions (with pushing to GitHub)?

Sure.

gmsorrow avatar Apr 04 '21 11:04 gmsorrow

@gmsorrow

I opened https://github.com/gmsorrow/eslint-plugin-modules-newline/pull/13

Before merging, you'll need to set the following env variables in CircleCI: GITHUB_TOKEN NPM_EMAIL NPM_TOKEN

I haven't tested this PR but a similar code works for my repos though they use Travis CI.

If the build fails due to generating an already published version, I recommend running git commit -m 'feat: an empty commit to test semantic release' --allow-empty --no-verify && git push origin master until the build passes because semantic release doesn't seem to recognize versions created manually.

oprogramador avatar May 31 '21 17:05 oprogramador