docs: document that plugins config is an override (#1216)
This patch documents that the `plugin` config option is an override, not a merge with the default. This is significant, for example, if you customise the github plugin as it will then prevent npm publishing by default unless the npm plugin is also defined manually.
This commit is contained in:
		
							parent
							
								
									01a0b2d08a
								
							
						
					
					
						commit
						228fed7a0b
					
				| @ -44,6 +44,8 @@ Each plugin must be configured with the [`plugins` options](./configuration.md#p | |||||||
| } | } | ||||||
| ``` | ``` | ||||||
| 
 | 
 | ||||||
|  | **Note:** If the `plugins` option is defined, it overrides the default plugin list, rather than merging with it. | ||||||
|  | 
 | ||||||
| ## Plugin ordering | ## Plugin ordering | ||||||
| 
 | 
 | ||||||
| For each [release step](../../README.md#release-steps) the plugins that implement that step will be executed in the order in which the are defined. | For each [release step](../../README.md#release-steps) the plugins that implement that step will be executed in the order in which the are defined. | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user