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

Using dependabot for poetry managed python project with requirements.txt export #7977

Open
1 task done
ajstewart opened this issue Sep 6, 2023 · 0 comments
Open
1 task done
Labels
T: feature-request Requests for new features

Comments

@ajstewart
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

Hi, I have a few repos were the python project is managed with poetry, however because of some specific CI deployments a requirements.txt is also generated (usually as a pre-commit hook) which some deployments then use instead of using poetry. Could also have different variants, e.g. tests-requirements.txt.

Now when dependabot opens PRs it only updates the pyproject.toml and poetry.lock files, and doesn't touch the requirements files, even if I place these in a different directory - which I thought could have been a solution. So I end up having to go into the PR to update the requirements.txt files before merging. I do see in the insights menu that dependabot recognises the .txt files but doesn't do anything with them.

I've searched a lot to try and find a solution, all I could come across was this old issue: #3458 that I believe is asking the same thing.

Of course there is the question of why use poetry in this case, but ignoring that, I wondered if I'm missing something that would make this possible or if it's currently a feature that just isn't there?

@ajstewart ajstewart added the T: feature-request Requests for new features label Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: feature-request Requests for new features
Projects
None yet
Development

No branches or pull requests

1 participant