mapbox / mapbox/mapbox-navigation-android
PR #7505 merged without review (mapbox-navigation-android)
Nobody has claimed this yet.
- 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/7505
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
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 pull request #7505 and the linked engineering best-practice guidance first. Determine which repository merge or review settings allowed the pull request to merge without approval, then verify that the repository requires an approving review before merging.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100