How can we schedule when the daily runs will be started?

Question

From on February 1, 2018 14:19

Recently (in the past ~2 weeks?) it appears that most of my repos are now being checked for new updates around 7am local time.

They used to be checked around 2am local time.

This is affecting my workflow because when I start work around 8am, my CI system is sometimes still busy working through all of the PRs (this was especially true today, because some of my "Monthly check" projects landed...and I had over 50 gem updates).

Is there a way that the dependabot PRs can be scheduled to occur earlier again? (at 2am local?)

Note: this seems to be repo-dependent..as some of my repos are done at different times of day...it just is a little disruptive because it used to be different, and (in my workflow) better.

Copied from original issue: dependabot/feedback#83

该提问来源于开源项目：dependabot/dependabot-core

Answer 1

I made a change recently that made Dependabot timezone aware, so it now creates PRs at 7am in whatever location your account has set (or the UK if it can’t figure it out).

I agree doing the update run a bit earlier would be a good thing, so I’m going to change it to 5am for everyone when I get some internet (I’m on holiday).

On 1 Feb 2018, at 07:19, Robin Dunlop wrote:

Recently (in the past ~2 weeks?) it appears that most of my repos are now being checked for new updates around 7am local time.

They used to be checked around 2am local time.

This is affecting my workflow because when I start work around 8am, my CI system is sometimes still busy working through all of the PRs (this was especially true today, because some of my "Monthly check" projects landed...and I had over 50 gem updates).

Is there a way that the dependabot PRs can be scheduled to occur earlier again? (at 2am local?)

Note: this seems to be repo-dependent..as some of my repos are done at different times of day...it just is a little disruptive because it used to be different, and (in my workflow) better.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.