You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure everything is correctly setup by running those tests first.
52
+
Make sure everything is correctly set up by running those tests first.
53
53
54
-
ESLint and Prettier are performed automatically on `git push`. However, we recommend you setup your IDE or text editor
54
+
ESLint and Prettier have performed automatically on `git push`. However, we recommend you set up your IDE or text editor
55
55
to run ESLint and Prettier automatically on file save. Otherwise, you should run them manually using:
56
56
57
57
```bash
58
58
npm run format
59
59
```
60
60
61
-
Alternatively you can setup your IDE to integrate with Prettier and ESLint for JavaScript and Markdown files.
61
+
Alternatively, you can set up your IDE to integrate with Prettier and ESLint for JavaScript and Markdown files.
62
62
63
63
To run the CLI locally:
64
64
@@ -68,10 +68,10 @@ To run the CLI locally:
68
68
69
69
## Architecture
70
70
71
-
The CLI is written using the [oclif](https://oclif.io/) cli framework and the [netlify/js-client](https://github.com/netlify/js-client) open-api derived API client.
71
+
The CLI is written using the [commander.js](https://github.com/tj/commander.js/) cli interface and the [netlify/js-client](https://github.com/netlify/js-client) open-api derived API client.
72
72
73
73
- Commands live in the [`src/commands`](src/commands) folder.
74
-
- The base command class which provides consistent config loading and an API client lives in [`src/utils/command.js`](src/utils/command.js).
74
+
- The base command class which provides consistent config loading and an API client lives in [`src/commands/base-command.js`](src/commands/base-command.js).
75
75
- Small utilities and other functionality live in [`src/utils`](src/utils).
76
76
77
77
A good place to start is reading the base command README and looking at the commands folder.
@@ -112,7 +112,7 @@ Merge the release PR
112
112
1. Create a branch named `releases/<tag>/<version>` with the version and tag you'd like to release.
113
113
2. Push the branch to the repo.
114
114
115
-
For example, a branch named `releases/rc/4.0.0` will create the version `v4.0.0-rc` and publish it under the `rc` tag.
115
+
For example, a branch named `releases/rc.0/4.0.0` will create the version `4.0.0-rc.0` and publish it under the `rc.0` tag.
0 commit comments