From 4b3e704d2cf298a2df144b45df8f8fcd9dd1f08f Mon Sep 17 00:00:00 2001 From: Floran Brutel <notFloran@users.noreply.github.com> Date: Wed, 29 May 2019 17:49:12 +0200 Subject: [PATCH] docs: Fix gitlab examples for Preset Hosting (#3834) --- website/docs/config-presets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/config-presets.md b/website/docs/config-presets.md index 3b241c9a7f..dc6334b992 100644 --- a/website/docs/config-presets.md +++ b/website/docs/config-presets.md @@ -37,8 +37,8 @@ The following namespace is used: - `@abc:xyz`: npm package `@abc/renovate-config` and preset `xyz` - `github>abc/foo`: github repository `https://github.com/abc/foo` and preset `default` - `github>abc/foo:xyz`: github repository `https://github.com/abc/foo` and preset `xyz` -- `gitlab>abc/foo`: gitlab repository `https://github.com/abc/foo` and preset `default` -- `gitlab>abc/foo:xyz`: gitlab repository `https://github.com/abc/foo` and preset `xyz` +- `gitlab>abc/foo`: gitlab repository `https://gitlab.com/abc/foo` and preset `default` +- `gitlab>abc/foo:xyz`: gitlab repository `https://gitlab.com/abc/foo` and preset `xyz` In general, GitHub or GitLab-based preset hosting is easier than npm because you avoid the "publish" step - simply commit preset code to the default branch and it will be picked up by Renovate the next time it runs. An additional benefit of using source code hosting is that the same token/authentication can be reused by Renovate in case you want to make your config private. -- GitLab