mapbox / mapbox/mapbox-navigation-android
PR #7630 merged without review (mapbox-navigation-android)
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
:wave: Hey there! It's [Changebot](https://github.com/mapbox/changebot), and I help repositories follow our [engineering](https://github.com/mapbox/engineering) best practices. My magic wand found some things I wanted to highlight for your review:
Item | Current status | Best practice guidelines
--- | --- | ---
Pull request state at time of merging | Without review | Approving review before merging
Merged by | @mapbox-github-ci-writer-public-1[bot] |
The following pull request was merged without a review: https://github.com/mapbox/mapbox-navigation-android/pull/7630
Can you take a look at these best practices and make any adjustments if needed?
Please tag `@mapbox/security-and-compliance` on this issue if you have any questions
Contributor guide
Research direction
Start by reviewing PR #7630 and the linked engineering best-practice guidelines to understand why it was merged without an approving review. Inspect the repository's review and merge controls, then confirm that the required review policy is enforced for future pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, kotlin
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100