mapbox / mapbox/mapbox-navigation-android
`update` Metalava baseline files automatically from CI if `check` steps are successful
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Follow-up ticket from https://github.com/mapbox/mapbox-navigation-android/pull/6254#pullrequestreview-1092403262 thread to keep track of 👇
> I suggest leaving this as is (i.e. `AddedMethod`s aren't reported anymore as they don't technically break SemVer) but updating the baseline files from CI automatically if the check steps are successful, so they are always up-to-date and conflicts won't be an option.
cc @mapbox/navigation-android @SevaZhukov
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 points to the PR 6254 review thread; read that thread first, then inspect the repository’s existing CI check steps and Metalava baseline files. Done means CI updates the baselines automatically only after the checks succeed, without leaving conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- ci-cd, mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100