docs: gitlab automerge docs (#6840)

This commit is contained in:
Umar Bari 2020-07-23 12:07:40 -06:00 committed by GitHub
parent 0823b14a5f
commit 7f5125d0e8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 18 additions and 0 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 66 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

View file

@ -100,3 +100,21 @@ Unlike on GitHub, it is not possible to have the option to install Renovate on "
##### Detecting new projects
Currently there is no detection mechanism in the backend scheduler to determine when Renovate has been added to a new project, so the onboarding MR won't appear instantly. Instead, the new project should be picked up during hourly scheduled runs.
##### Auto merging pull requests
If you have auto merging enabled in your config, Renovate needs permission to merge a branch into master.
There's four ways to make it work:
- Allow all developers to merge into master branch
![Allow renovate-bot merge permission](assets/images/allow-developers-to-merge.png)
- Change renovate-bot member permission from developer to **maintainer**
![Allow renovate-bot merge permission](assets/images/change-renovate-bot-to-maintainer.png)
- Allow **renovate-bot** to merge into master.
![Allow renovate-bot merge permission](assets/images/allow-renovate-bot-to-merge.png)
- Change master branch from protected branch to **unprotected** branch
![Allow renovate-bot merge permission](assets/images/unprotect-master-branch.png)