Stricter breaking change detection rules
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 26
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
As of now the configured category of rules is WIRE, which is the most permissive one. We should look into using one of the more stricter categories -
FILE > PACKAGE > WIRE_JSON > WIRE
One reason for us to move to WIRE_JSON would be for detecting changes that would break pipelines that use Beast.
Contributor guide
No contributing guide indexed for this repository
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
Review the configured Buf breaking-change category and the FILE > PACKAGE > WIRE_JSON > WIRE ordering described in the issue, then assess which changes Beast pipelines need protected against. Done means choosing an appropriate category and documenting or validating the resulting configuration; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100