The main branch can contain unreleased code. This merge request will make sure that for scheduled pipeline builds we automatically check out the last tag revision so that we run the build job and the example build job on that revision. This is because we need to pick a target branch or tag for our scheduled pipelines and this is not dynamic, meaning that we can't say: pick the last tag. We have to select a static tag or branch. It makes sense to pick the main branch in that case.
I created a scheduled pipeline as a test. The pipeline results can be found here:
I deleted the scheduled pipeline to make sure we don't run it again until this code has been approved and merged.
Note that after we merge this MR, we still need to set up the scheduled pipeline again. My proposal would be to set this up for every Monday 4:30am (exactly 24 hours after the weekly scheduled pipeline of the Docker Images repo).
