Ensure binary compatibility for every change on CI.
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
Going forward, I think we should use a tool such as the binary compatibility validator plugin to avoid making unconscious binary-incompatible changes to the library API.
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
The issue names no repository files or CI entry point. Start by reviewing the existing CI configuration and the Kotlin binary-compatibility-validator documentation; done means every change is checked for binary compatibility in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100