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

Versionist should be able to update itself with a simple script action #64

Closed
lekkas opened this issue Dec 20, 2016 · 4 comments
Closed

Comments

@lekkas
Copy link
Contributor

lekkas commented Dec 20, 2016

It'd be nice if we had an easy way , like a package.json script, to run npm run versionist on this very repo

@lurch
Copy link
Contributor

lurch commented Dec 20, 2016

I thought the versionist CHANGELOG was already being updated by versionist itself?

@lekkas
Copy link
Contributor Author

lekkas commented Dec 20, 2016

It is, this issue is very low priority since one can just run./bin/cli.js

@lekkas lekkas changed the title Versionist should be able to update itself Versionist should be able to update itself with a simple script action Dec 20, 2016
@lurch
Copy link
Contributor

lurch commented Dec 20, 2016

Ahh, now I see :) I didn't realise there wasn't a local ./versionist command available (i.e. according to the README you need to install versionist globally, before running it for the first time)

@lekkas
Copy link
Contributor Author

lekkas commented Dec 20, 2016

;) Yeah it's just that this creates a chicken and egg situation (kind of), where you'd need to run npm i -g . to run versionist on the versionist repo for the latest changes to come into effect. A minor issue really

lurch added a commit that referenced this issue Dec 20, 2016
So that versionist can be run on itself, without needing to be installed
globally.

Fixes #64

Change-Type: minor
lurch added a commit that referenced this issue Dec 21, 2016
So that versionist can be run on itself, without needing to be installed
globally.

Fixes #64

Change-Type: minor
@lurch lurch closed this as completed in #66 Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants