Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(datasources): rewrite intro #15725

Merged
merged 2 commits into from
May 26, 2022
Merged

docs(datasources): rewrite intro #15725

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f055f7d
docs(datasources): rewrite intro
HonkingGoose May 25, 2022
49347c0
Simplify sentences
HonkingGoose May 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/usage/modules/datasource.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,11 @@ title: Datasources

# Datasources

Once Renovate's manager is done scanning files and extracting dependencies, it will assign a `datasource` to each extracted package file and/or dependency so that Renovate then knows how to search for new versions.
You do not need to ever configure/override datasources directly, but you may use them in a `packageRules` array to configure other aspects of Renovate's behavior, e.g.
After Renovate's manager scanned the files and extracted the dependencies, it assigns a `datasource` to each extracted package file or dependency.
The `datasource` tells Renovate how to search for new versions.

You don't need to configure or override datasources.
But you may use datasources in a `packageRules` array to configure Renovate's behavior, for example:

```json
{
Expand Down