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

Automatically check for update #10

Open
mschwartz opened this issue Jun 14, 2018 · 5 comments
Open

Automatically check for update #10

mschwartz opened this issue Jun 14, 2018 · 5 comments

Comments

@mschwartz
Copy link
Contributor

Description

modus-cli should periodically check for updates (to see if a newer version exists)

@mschwartz
Copy link
Contributor Author

The package.json file can be downloaded and version checked against the existing one.

@mschwartz
Copy link
Contributor Author

Related issue is that if modus-cli is used to download/merge guidelines, we can check the guidelines repo periodically to see if IT changed, too.

@grgur
Copy link
Member

grgur commented Jun 14, 2018

This would be nice. How would we track changes, tho? E.g.

  1. Repo XYZ clones samples from Guidelines
  2. Repo XYZ changes LICENSE
  3. LICENSE is updated in Guidelines
  4. Now what? How does modus-cli know that LICENSE is changed but e.g. ISSUE_TEMPLATE isn't?

@mschwartz
Copy link
Contributor Author

mschwartz commented Jun 14, 2018

We keep a version number in modus-cli-config.js and compare with version number in the guidelines repo.

If LICENSE exists, cli won't overwrite it unless you add the -o switch.

@grgur
Copy link
Member

grgur commented Jun 14, 2018

That would be nice. We need to prioritize all feature requests first

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

No branches or pull requests

2 participants