[ci] Add a CI check for lock files on the `earlgrey_1.0.0` branch
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
On the master branch, we automatically check in CI that some locks files (bazel module lock file notably) is clean. This check should probably be backported to the `earlgrey_1.0.0` branch.
See https://github.com/lowRISC/opentitan/pull/30146#discussion_r3465246574 for an instance where it would have caught a problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing lock-file check on the master branch and compare it with the earlgrey_1.0.0 branch. Review the linked pull request discussion for the Bazel module lock-file failure, then verify that the backported CI check detects unclean lock files on the target branch.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100