lowRISC / lowRISC/opentitan-provisioning
[quality] improve include guard checking implementation
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 16
- Forks
- 13
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 18
Description
The include guard check / fix Bazel rules (added in #40) execute a Python script on the local system. These should be enhanced to:
- [ ] run the script via a Bazel managed python toolchain and py_binary target, and
- [ ] accept the project names as a command line arg.
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 with the include guard check and fix Bazel rules added in issue #40, then trace how they invoke the local Python script. Review the repository's Bazel Python toolchain and py_binary usage before changing the rules. Done means the script runs through a Bazel-managed Python target and accepts project names as a command-line argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100