Context
PR #3 introduced pr-checks.yml with a pinned nightly toolchain for reproducible PR results.
During review, @lh-sag suggested that tracking latest nightly
Rust changes fits better as a scheduled job rather than a PR check, since unpinned nightly
advances daily and would make PR results non-reproducible.
Goal
Add a scheduled CI workflow that:
- Runs
cargo clippy and cargo fmt against the latest nightly toolchain
- Triggers on a cron schedule (e.g. weekly or nightly)
- Automatically opens a GitHub issue when new warnings/errors are found, with details of
the findings so they can be triaged and fixed before the pinned toolchain is advanced
Considerations
- Will it help developers, or will it create confusion?
- Runner cost: scheduled jobs consume CI minutes independently of PRs, schedule frequency
should be agreed before implementation
- Auto issue creation: needs a GitHub token with
issues: write permission and de-duplication
logic (avoid opening duplicate issues if a previous one is still open)
Related
Context
PR #3 introduced
pr-checks.ymlwith a pinned nightly toolchain for reproducible PR results.During review, @lh-sag suggested that tracking latest nightly
Rust changes fits better as a scheduled job rather than a PR check, since unpinned nightly
advances daily and would make PR results non-reproducible.
Goal
Add a scheduled CI workflow that:
cargo clippyandcargo fmtagainst the latestnightlytoolchainthe findings so they can be triaged and fixed before the pinned toolchain is advanced
Considerations
should be agreed before implementation
issues: writepermission and de-duplicationlogic (avoid opening duplicate issues if a previous one is still open)
Related
eclipse-opensovd/cicd-workflowsfor potential shared implementation