PR #7828 merged without review (mapbox-navigation-android)

Open
#7,830 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Domain
ci-cd

Research direction

Start by reviewing pull request #7828 and the linked engineering best-practice guidelines to understand why it merged without review. Confirm whether repository changes are needed and define completion as preventing merges without an approving review; no source files or tests are named in the issue.

Written by the indexing model from the issue text.

Description

👋 Hey there! It's Changebot, and I help repositories follow our 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/7828

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

Dominant language
Kotlin
Stars
651
Forks
321
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/mapbox-navigation-android

All issues in mapbox/mapbox-navigation-android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.