[gitlab] Return early from scheduled gitlab jobs when there haven't been any recent commits

One other thing this would do would be to allow us to leave security-only core branches on daily schedule without worrying about the resource consumption too much. Currently on DrupalCI we manually move the security-only branches to on-commit, since they might only get one commit per month, then manually move them to no testing once they're EOL. If we implement this, we can set up a scheduled run for a branch when we open it, and leave it the same until the branch is EOL.

Thanks @catch

I do like the idea of not running this on the weekend, but then again, not everyone shares the same idea for a weekend. I don't know enough abut the GitLab interaction to know if there's a way to check for commits.

Maybe there would be folks from GitLab who might have ideas on their side about how to reduce their server usage.

Does seem to be the kind of thing that should be part of a good aproach to ESG. https://about.gitlab.com/environmental-social-governance/

I don't know enough abut the GitLab interaction to know if there's a way to check for commits.

The gitlab pipeline lets us run arbitrary bash commands and do things dependent on the results. So although we can't stop a pipeline from starting without upstream features from gitlab, I'm sure we can exit early if we check git commit history ourselves, which would still save most of the computing time.

We already have arbitrary bash which doesnt even start a pipeline if false. This is keeps noise out of the UI. See https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/include...