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

Figure out a better way to update requirements via CI #51

Closed
gerrymanoim opened this issue Jul 7, 2021 · 1 comment
Closed

Figure out a better way to update requirements via CI #51

gerrymanoim opened this issue Jul 7, 2021 · 1 comment
Labels
CI Continuous integration

Comments

@gerrymanoim
Copy link
Owner

Dependabot cannot be made to look at a single file (only a single directory). For now, I'd like to keep the older lock file around, but aggressively update the newer one.

Some options:

  1. Move each individual requirement to a subfolder (does dependabot need requirements_locked and requirements.in to be in the same place?).
  2. Only use a lock file for the "old" dependencies (this would cause breakage in unrelated PRs).
  3. ???

Leaning to option 1.

@maread99 maread99 added the CI Continuous integration label Jun 28, 2022
@maread99
Copy link
Collaborator

Closed as superseded by #238.

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

No branches or pull requests

2 participants