From aee4044cd057854a08627726badc5e3f20eddf4d Mon Sep 17 00:00:00 2001
From: Rhys Arkins <rhys@arkins.net>
Date: Fri, 12 Apr 2019 14:35:43 +0200
Subject: [PATCH] docs: update devDependencies automerge example
Closes #3536
---
website/docs/configuration-options.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/website/docs/configuration-options.md b/website/docs/configuration-options.md
index fde753b7bf..b19064bdd8 100644
--- a/website/docs/configuration-options.md
+++ b/website/docs/configuration-options.md
@@ -43,9 +43,10 @@ Usually you won't want to automerge _all_ PRs, for example most people would wan
Also note that this option can be combined with other nested settings, such as dependency type. So for example you could elect to automerge all `devDependencies` only this way:
```json
- "devDependencies": {
+ "packageRules": [{
+ "depTypeList": ["devDependencies"],
"automerge": true
- }
+ }]
```
Warning: GitHub currently has a bug where automerge won't work if a GitHub Organization has protected their master branch, and there is no way to configure around this. Hence, automerging will try and fail in such situations. This doc will be updated once that bug/limitation is fixed by GitHub.
--
GitLab