tools: offset GitHub crons by 3 minutes

[targos]

It might increase the chance of them being scheduled.

Refs: nodejs/build#4443
Refs: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[sxa]

Looks like you've removed the quote marks around this - was that intentional?

But no objection otherwise from me - whether it would prevent it being scheduled for hours I'm a bit sceptical about but I don't see any negatives on it so worth a try.

[targos]

I removed the quote marks because the linter complained abouth them: https://github.com/nodejs/node/actions/runs/33155298528/job/98796532067

I'm sceptical too, but I don't know what else to do. This PR is based on this sentence from the GitHub documentation:

The schedule event can be delayed during periods of high loads of GitHub Actions workflow runs. High load times include the start of every hour. If the load is sufficiently high enough, some queued jobs may be dropped. To decrease the chance of delay, schedule your workflow to run at a different time of the hour.

[sxa]

I removed the quote marks because the linter complained about them:

That seems a bit odd given that the examples in the docs have quotes (albeit single) in them.

I'm sceptical too, but I don't know what else to do.

yeah that's reasonable ... As I say there shouldn't be any negatives from this. I've just triggered a manual PR test on #62251 because it hadn't triggered from the request-ci label after 13 hours...

[sxa]

If my experience of it not triggering at all is the same for other people's PRs then we might as well put this in and see if anything objects to the absent quotes. I'm just a little nervous about the (hopefully small) risk of it not triggering because of that.

Although we've had a few triggers overnight so we should notice if we get none!

[github-actions]

Fast-track has been requested by @panva. Please 👍 to approve.

[panva]

The quotes are optional. YAML parses the unquoted value as a string.

I don't believe this is going to do anything but it's worth a try and as @targos said it's about the only thing we can do outside of having a cron in jenkins trigger this through workflow_dispatch which comes with its own slew of considerations.

[aduh95]

Is 3 arbitrary or based on something? In any case, it doesn't cost much to try

[panva]

Landed in 523e583

[targos]

Is 3 arbitrary or based on something? In any case, it doesn't cost much to try

Arbitrarily chosen by me.