Skip to content

Latest commit

 

History

History
38 lines (26 loc) · 1.12 KB

.verb.md

File metadata and controls

38 lines (26 loc) · 1.12 KB

Tasks

Tasks are modularized in an effort to make it as easy as possible for you to create your own a-la-carte updater experience. As such:

  • some tasks update one specific file
  • some tasks update multiple files
  • some tasks are just aliases for running "groups" of tasks

Running tasks

To run a task, just run $ update git-tags: followed by the name of the task to run. For example, either of the following commands can be used to run the git-tags task:

$ update {%= alias %}:git-tags
$ update {%= alias %}:default

Available tasks

{%= increaseHeadings(apidocs("updatefile.js")) %}

[docs]: {%= platform.docs %}/

Next steps

Running unit tests

It's never too early to begin running unit tests. When you're ready to get started, the following command will ensure the project's dependencies are installed then run all of the unit tests:

$ npm install && test

Publishing your project

If you're tests are passing and you're ready to publish your project to npm, you can do that now with the following command:

Are you sure you're ready?!

$ npm publish