chore: adding dummy commit to refresh scheduler

[Freyskeyd]

Description

Add a github action to push a commit every 15 days in order to refresh the scheduler timeout.

PR Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added or updated tests that comprehensively prove my change is effective or that my feature works

[dvdplm]

Can you help me understand better what this does? Or rather, what is the problem that it solves?

[Freyskeyd]

The issue that this GitHub action will solve is the issue with the current rust_builder which build nightly docker image every day, after 60 days without action on the repo (commit) all workflows are disabled and need to be re-enable manually. Having a GitHub action that push a commit every 15 days solve this.

[dvdplm]

I see, thank you. Do you mind adding this info to the workflowfile itself (as a comment) so we readers. know what it's for?

[sebastiendan]

I don't think we need a PAT here. If default permissions of the default GITHUB_TOKEN aren't enough, you can set contents to write and it should be enough.
https://docs.github.com/en/actions/security-guides/automatic-token-authentication

[Freyskeyd]

The point of adding this PAT was to allow the commit to trigger workflow (which isn't the case when you checkout with the default one) but maybe we don't need this job to trigger workflow. I don't know if it gonna work as there is no documentation on that :x

[sebastiendan]

Ok interesting. But indeed we don't need to trigger a workflow here, we just need to update history so that the cronjob continues working.