ExternalVendorCode/balena-cli
1
0
Fork 0
mirror of https://github.com/balena-io/balena-cli.git synced 2024-12-19 21:57:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md re balena-dev workflow

Browse Source 
Change-type: patch
This commit is contained in:
Paulo Castro 2020-10-03 00:16:29 +01:00
parent 2974c203b5
commit 8978221866
1 changed files with 0 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
CONTRIBUTING.md
View File

@ -21,31 +21,6 @@ Before opening a PR, test your changes with `npm test`. Keep compatibility in mi
meant to run on Linux, macOS and Windows. balena CI will run test code on all three platforms, but
this will only help if you add some test cases for your new code!
## ./bin/balena-dev and oclif
When using `./bin/balena-dev`, it is currently necessary to manually edit the `oclif` section of
`package.json` to replace `./build` with `./lib` as follows:
Change from:
```
"oclif": {
"commands": "./build/commands",
"hooks": {
"prerun": "./build/hooks/prerun/track"
```
To:
```
"oclif": {
"commands": "./lib/commands",
"hooks": {
"prerun": "./lib/hooks/prerun/track"
```
And then remember to change it back before pushing the pull request. This is obviously error prone
and inconvenient, and improvement suggestions are welcome: is there a better solution than
automatically editing `package.json`? It is doable, if it is what needs to be done.
## Semantic versioning, commit messages and the ChangeLog
The CLI version numbering adheres to [Semantic Versioning](http://semver.org/). The following