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

Move to continuous deployment #388

Closed
orta opened this Issue Nov 15, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@orta
Copy link
Member

orta commented Nov 15, 2017

It's a library, so individual clients like force/positron update when it makes sense for them, we should just deploy on every master commit to npm.

@orta

This comment has been minimized.

Copy link
Member

orta commented Nov 15, 2017

Should do #189 at the same time

@damassi

This comment has been minimized.

Copy link
Member

damassi commented Feb 2, 2018

@orta

This comment has been minimized.

Copy link
Member

orta commented Feb 2, 2018

I'm not sure if you can persuade everyone to move to the commit pattern ( I use it for a few danger plugins ) if you can, I'm definitely game 👍

@damassi

This comment has been minimized.

Copy link
Member

damassi commented Feb 24, 2018

Semantic release has been added in #521

@damassi damassi closed this Feb 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment