lowRISC / lowRISC/opentitan-provisioning
[ci] add proto lint check to block breaking proto changes
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 16
- Forks
- 13
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 18
Description
To enforce stability across protos we should add a CI check. The [buf](https://buf.build/docs/breaking/overview) tool seems like a logical choice to enforce such checks.
CC: @shmulik-h
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 reviewing the repository's existing CI configuration and the linked buf breaking-change documentation. Add a proto compatibility check that fails CI for breaking changes, then verify it with compatible and breaking proto changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100