We should change the interval of our dependabot PRs to monthly, to reduce the frequency with which we need to merge them.
Original discussion below:
We should automatically merge our dependabot PRs with passing checks, using the merge me GitHub Action.
This will cut down considerably on developer time each sprint.
@zackkrida
Sometimes, it so happens with dependabot that it says code coverage - unknown in its PR. I'm not sure if this affects anything at all, but this deters me from auto-merging a dependabot PR (in my other personal repo's).
Although this may not be the orthodox way of solving this problem, I would suggest:
interval: "weekly" attribute in the .github/dependabot.yml to monthly. Most OSS organisations prefer having it monthly (afaik).@nimishbongale I'm a little skeptical of auto-merging too. The fact that our deployment process is manual makes me less skeptical, but I'll think about it more. I think your suggestions are good compromises.
If we had automated visual testing, merging automatically would not be much of a question. But even in manual deployment, it isn't feasible to individually verify that everything is working as before (and this infeasibility only increases with more components being added to the package).
@dhruvkb Agreed. Like I said on the vocab call I think switching the interval to monthly like @nimishbongale is the best path forward.
I can take this on. Is this change's scope only PRs in vocabulary or all CC repos?
@akmadian
I think it was discussed particularly to do with vocabulary, as I'm not sure about the others (if they want the frequency to be changed ie.)
Most helpful comment
@dhruvkb Agreed. Like I said on the vocab call I think switching the interval to
monthlylike @nimishbongale is the best path forward.