Skip to content

Only run dependabot on the "main" requirements.txt #296

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

Merged
merged 1 commit into from
Jun 1, 2023

Conversation

mdboom
Copy link
Contributor

@mdboom mdboom commented May 30, 2023

You can't exclude directories for dependabot, only exclude them, (thanks @hugovk for discovering that), so by moving the main requirements.txt to a directory that doesn't include all of the benchmarks' requirements.txt beneath it, we can limit dependabot to just that one file.

You can't exclude directories for dependabot, only exclude them, so
by moving the main requirements.txt to a directory that doesn't
include all of the benchmarks' requirements.txt beneath it, we can
limit dependabot to just that one file.
@mdboom mdboom requested a review from hugovk May 30, 2023 16:09
@AlexWaygood AlexWaygood changed the title Only run dependabot the "main" requirements.txt Only run dependabot on the "main" requirements.txt May 30, 2023
@hugovk hugovk merged commit 45730c0 into python:main Jun 1, 2023
@hugovk
Copy link
Member

hugovk commented Jun 1, 2023

Hmm, after merge, https://github.com/python/pyperformance/runs/13917712436 reports it's invalid:

Your .github/dependabot.yml contained invalid details
Dependabot encountered the following error when parsing your .github/dependabot.yml:

The property '#/updates/0' did not contain a required property of 'schedule'
Please update the config file to conform with Dependabot's specification.

Let's add a schedule value:

https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#configuration-options-for-dependabotyml

@hugovk
Copy link
Member

hugovk commented Jun 1, 2023

Please see #298 as a followup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants