Implement workflows for dependency updates #979
Conversation
These workflows are similar to the ones in the OPTIMADE Gateway (see https://github.com/Materials-Consortia/optimade-gateway). The following is done: - Run Dependabot updates every Monday at 5 UTC. - Merge into/reset permanent, dedicated dependabot branch whenever there is a new push to `master` (the default branch). - Create a PR every Wednesday at 6:30 UTC, requesting to merge a copy of the dedicated dependabot branch into `master`. As a bonus, before opening this PR, an attempt is made at also updating the `pre-commit` hooks and running `pre-commit` to commit any changes. - Enable "auto-merge" for all Dependabot-created PRs. Remaining issues/manual labour: - Update `setup.py` with dependencies according to the Wednesday PR. - Fix `pre-commit` if issues arise when running it. - Fix Dependabot dependency PRs if they do not pass the CI tests.
Codecov Report
@@ Coverage Diff @@
## master #979 +/- ##
=======================================
Coverage 92.92% 92.92%
=======================================
Files 67 67
Lines 3787 3787
=======================================
Hits 3519 3519
Misses 268 268
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Need to checkout repository.
There was a problem hiding this comment.
This will definitely save some time, thanks @CasperWA!
Couple of general comments:
- I can foresee is occasionally we have to manually ask dependabot to recreate PRs after another PR has been merged into
dependabot_updates. We can see how we go with it though. - What happens if we don't merge the Wednesday PR before the next one is created? It looks like the dependabot branch gets reset either way?
A few specific comments:
It might. However, since we're not making changes to the PRs when activating the auto-merge it shouldn't be crucial.
Bad things could happen I think. I haven't tested this. Although I think it may just delete/overwrite the |
Closes #958
These workflows are similar to the ones in the OPTIMADE Gateway (see https://github.com/Materials-Consortia/optimade-gateway).
The following is done:
master(the default branch).master.As a bonus, before opening this PR, an attempt is made at also updating the
pre-commithooks and runningpre-committo commit any changes.Remaining issues/manual labour:
setup.pywith dependencies according to the Wednesday PR.pre-commitif issues arise when running it.