Skip to content

Commit

Permalink
docs(config-presets): use inline code for preset patterns (#32622)
Browse files Browse the repository at this point in the history
  • Loading branch information
risu729 authored Nov 19, 2024
1 parent c80a052 commit 865ce91
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/usage/config-presets.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ To host your preset config on GitHub:

- Create a new repository. Normally you'd call it `renovate-config` but it can be named anything
- Add configuration files to this new repo for any presets you want to share. For the default preset, `default.json` will be checked. For named presets, `<preset-name>.json` will be loaded. For example, loading preset `library` would load `library.json`. No other files are necessary.
- In other repos, reference it in an extends array like "github>owner/name", for example:
- In other repos, reference it in an extends array like `"github>owner/name"`, for example:

```json
{
Expand All @@ -195,7 +195,7 @@ 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
- Add a `default.json` to this new repo containing the preset config. No other files are necessary
- In other repos, reference it in an extends array like "gitlab>owner/name", e.g. "gitlab>rarkins/renovate-config"
- In other repos, reference it in an extends array like `"gitlab>owner/name"`, e.g. `"gitlab>rarkins/renovate-config"`

## Gitea-hosted Presets

Expand Down

0 comments on commit 865ce91

Please sign in to comment.