You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1523 started running the CI tests on a periodic basis to identify integration problems with dependencies or other libraries. Ideally we'd only run the CI tests when one of the dependencies actually changes. Otherwise we're wasting resources. I think the best option for this is to use Dependabot.
I think it'd be possible to do by using pip-tools and creating a requirements_ci.in and requirements_ci.txt file. This file would contain all the dependencies listed within the tox.ini file. The goal is to have Dependabot identify the changes in that requirements file, then create a PR which will run CI, thus identifying integration problems.
If we do go this route, I think it'd be a good idea to use the auto-merge functionality such that it will automatically merge these PRs specifically when they pass.
The text was updated successfully, but these errors were encountered:
#1523 started running the CI tests on a periodic basis to identify integration problems with dependencies or other libraries. Ideally we'd only run the CI tests when one of the dependencies actually changes. Otherwise we're wasting resources. I think the best option for this is to use Dependabot.
I think it'd be possible to do by using pip-tools and creating a
requirements_ci.in
andrequirements_ci.txt
file. This file would contain all the dependencies listed within thetox.ini
file. The goal is to have Dependabot identify the changes in that requirements file, then create a PR which will run CI, thus identifying integration problems.If we do go this route, I think it'd be a good idea to use the auto-merge functionality such that it will automatically merge these PRs specifically when they pass.
The text was updated successfully, but these errors were encountered: