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.

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

docs(python): drop duplicate fileMatch info #28146

Merged
merged 1 commit into from Mar 26, 2024
Merged
Changes from all commits
Commits
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
18 changes: 0 additions & 18 deletions docs/usage/python.md
Expand Up @@ -23,24 +23,6 @@ Legacy versions with the `===` prefix are ignored.
1. Renovate searches for the latest version on [PyPI](https://pypi.org/) to decide if there are upgrades
1. If the source package includes a GitHub URL as its source, and has a "changelog" file _or_ uses GitHub releases, a Release Note will be embedded in the generated PR

## Alternative file names

For the `pip_requirements` manager, the default file matching regex for `requirements.txt` follows common file name conventions.

It will match `requirements.txt` and `requirements.pip`, and any file in the format `requirements-*.txt` or `requirements-*.pip`, to allow for common filename patterns such as `requirements-dev.txt`.

But Renovate may not find all your files.

You can tell Renovate where to find your file(s) by setting your own `fileMatch` regex:

```json title="Setting a custom fileMatch regex"
{
"pip_requirements": {
"fileMatch": ["my/specifically-named.file", "\\.requirements$"]
}
}
```

## Alternate registries

By default Renovate checks for upgrades on the `pypi.org` registry.
Expand Down