mapbox / mapbox/mapbox-navigation-android
PR #7614 merged without successful status checks (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 | Required? | Best practice guidelines
--- | --- | --- | ---
Run unsuccessful: [ci/circleci: release-workflow/release-snapshot-start](https://circleci.com/workflow-run/572f5e5d-dfe9-4468-bba2-c790237202ff) | pending | optional | success
Run unsuccessful: [ci/circleci: default/mobile-metrics-dry-run](https://circleci.com/workflow-run/d38195ae-d914-425e-b79c-6f4e933af67b) | pending | optional | success
Run unsuccessful: [default](https://github.com/mapbox/mapbox-navigation-android/runs/18633537082) | null | optional | success
Run unsuccessful: [publisher-deployer](https://github.com/mapbox/mapbox-navigation-android/runs/18632279373) | neutral | optional | success
Run unsuccessful: [release-workflow](https://github.com/mapbox/mapbox-navigation-android/runs/18632277716) | null | optional | success
The following PR was merged without the status checks passing: https://github.com/mapbox/mapbox-navigation-android/pull/7614
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 PR #7614 and the linked CircleCI and GitHub workflow runs to determine why unsuccessful optional checks allowed the merge. Trace the repository's merge and status-check configuration; done means the relevant checks have the intended outcomes before a pull request can be merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100