mapbox / mapbox/mapbox-navigation-android

PR #7549 merged without successful status checks (mapbox-navigation-android)

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

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/7f160b99-130c-4c45-81a1-676bdbbaafc4) | pending | optional | success
Run unsuccessful: [ci/circleci: default/mobile-metrics-dry-run](https://circleci.com/workflow-run/6a5e3da2-f2b1-45d9-afe3-e951fa3d7666) | pending | optional | success
Run unsuccessful: [publisher-deployer](https://github.com/mapbox/mapbox-navigation-android/runs/17639978947) | neutral | optional | success
Run unsuccessful: [process](https://github.com/mapbox/mapbox-navigation-android/actions/runs/6495296664/job/17639978728) | skipped | optional | success
Run unsuccessful: [default](https://github.com/mapbox/mapbox-navigation-android/runs/17639977871) | null | optional | success
Run unsuccessful: [release-workflow](https://github.com/mapbox/mapbox-navigation-android/runs/17639977752) | null | optional | success

The following PR was merged without the status checks passing: https://github.com/mapbox/mapbox-navigation-android/pull/7549

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

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.

Research direction

Review the release-workflow and default/mobile-metrics-dry-run CircleCI runs, along with the publisher-deployer, process, default, and release-workflow GitHub Actions runs linked in the issue. Determine why PR #7549 was merged without successful optional checks. Done means the relevant checks are configured and enforced consistently before merge.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.