docs: fix default values for managers

This commit is contained in:
Rhys Arkins 2018-04-18 06:43:21 +02:00
parent f408d582e8
commit 9917b603cf

View file

@ -109,10 +109,10 @@ It's possible to add this setting into the `renovate.json` file as part of the "
Configuration specific for bazel WORKSPACE updates. Configuration specific for bazel WORKSPACE updates.
| name | value | | name | value |
| ------- | ----------------- | | ------- | ------ |
| type | object | | type | object |
| default | { enabled: true } | | default | {} |
## branchName ## branchName
@ -163,10 +163,11 @@ Set this value to 'patch', 'minor' or 'major' to have Renovate update the versio
Configuration object for CircleCI yaml file renovation. Also inherits settings from `docker` object. Configuration object for CircleCI yaml file renovation. Also inherits settings from `docker` object.
| name | value | | name | value |
| ------- | ----------------- | | ------------- | ------ |
| type | object | | type | object |
| default | { enabled: true } | | default | {} |
| parentManager | docker |
## commitBody ## commitBody
@ -308,19 +309,20 @@ Add to this object if you wish to define rules that apply only to PRs that pin D
Configuration specific for Dockerfile updates. Configuration specific for Dockerfile updates.
| name | value | | name | value |
| ------- | --------------------------------------------- | | ------- | ------------------------------ |
| type | object | | type | object |
| default | { enabled: true, major: { enabled: false }, } | | default | { major: { enabled: false }, } |
## docker-compose ## docker-compose
Configuration object for Docker Compose yaml file renovation. Also inherits settings from `docker` object. Configuration object for Docker Compose yaml file renovation. Also inherits settings from `docker` object.
| name | value | | name | value |
| ------- | ----------------- | | ------------- | ------ |
| type | object | | type | object |
| default | { enabled: true } | | default | {} |
| parentManager | docker |
## enabled ## enabled
@ -620,10 +622,10 @@ This value defaults to empty string, as historically no prefix was necessary for
Configuration specific for meteor updates. Configuration specific for meteor updates.
| name | value | | name | value |
| ------- | ------------------ | | ------- | ------ |
| type | object | | type | object |
| default | { enabled: false } | | default | {} |
Set enabled to `true` to enable meteor package updating. Set enabled to `true` to enable meteor package updating.
@ -664,10 +666,10 @@ Check out our [Node.js documentation](https://renovateapp.com/docs/language-supp
Configuration specific for npm dependency updates (`package.json`). Configuration specific for npm dependency updates (`package.json`).
| name | value | | name | value |
| ------- | ----------------- | | ------- | ------ |
| type | object | | type | object |
| default | { enabled: true } | | default | {} |
## npmToken ## npmToken
@ -695,10 +697,11 @@ See https://renovateapp.com/docs/deep-dives/private-modules for details on how t
Configuration specific for `.nvmrc` files. Configuration specific for `.nvmrc` files.
| name | value | | name | value |
| ------- | ----------------- | | ------------- | ------ |
| type | object | | type | object |
| default | { enabled: true } | | default | { } |
| parentManager | node |
For settings common to all node.js version updates (e.g. travis, nvm, etc) you can use the `node` object instead. For settings common to all node.js version updates (e.g. travis, nvm, etc) you can use the `node` object instead.
@ -1190,10 +1193,11 @@ It is only recommended to set this field if you wish to use the `schedules` feat
Configuration specific for `.travis.yml` files. Configuration specific for `.travis.yml` files.
| name | value | | name | value |
| ------- | ------------------ | | ------------- | ------------------ |
| type | object | | type | object |
| default | { enabled: false } | | default | { enabled: false } |
| parentManager | node |
For settings common to all node.js version updates (e.g. travis, nvm, etc) you can use the `node` object instead. For settings common to all node.js version updates (e.g. travis, nvm, etc) you can use the `node` object instead.