renovate/renovate
1
0
Fork 0
mirror of https://github.com/renovatebot/renovate.git synced 2025-01-12 06:56:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

Mention access level for private GitLab repositories (#11357)

Browse source 
With a Guest level access Renovate is not able to access the repository.

See https://docs.gitlab.com/ee/user/permissions.html
This commit is contained in:
Mathias Brodala 2021-08-20 19:50:37 +02:00 committed by GitHub
parent 1a82293c6d
commit e3778043c1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/usage/config-presets.md
View file

@ -149,6 +149,8 @@ You do not need to add it as a devDependency or add any other files to the prese
It is also possible to host your preset config using just a regular GitLab repository and without needing to publish it to npmjs.
In such cases Renovate will simply look for a `default.json` file in the default branch.
For a private GitLab repository Renovate requires at least _Reporter_ level access.
To host your preset config on GitLab:
- Create a new repository on GitLab. Normally you'd call it `renovate-config` but it can be named anything
@ -182,6 +184,8 @@ But you also probably want the preset to be private too, so how can the other re
The answer is to host your preset using GitHub or GitLab - not npmjs - and make sure you have added the preset's repo to Renovate too.
GitHub will then allow Renovate to access the preset repo whenever it is processing any other repos within the same account/org.
For a private GitLab repository Renovate requires at least _Reporter_ level access.
## Contributing to presets
Have you configured a rule that you think others might benefit from?