mapbox / mapbox/mapbox-navigation-android
PR #7582 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/568a031d-92fb-45dd-8b64-b2ed236ae4d9) | pending | optional | success
Run unsuccessful: [ci/circleci: default/mobile-metrics-dry-run](https://circleci.com/workflow-run/fc78904c-9ce3-45df-9890-3e3b512a47f3) | pending | optional | success
Run unsuccessful: [process](https://github.com/mapbox/mapbox-navigation-android/actions/runs/6665070228/job/18113932680) | skipped | optional | success
Run unsuccessful: [publisher-deployer](https://github.com/mapbox/mapbox-navigation-android/runs/18113931563) | neutral | optional | success
Run unsuccessful: [default](https://github.com/mapbox/mapbox-navigation-android/runs/18113930463) | null | optional | success
Run unsuccessful: [release-workflow](https://github.com/mapbox/mapbox-navigation-android/runs/18113930373) | null | optional | success
The following PR was merged without the status checks passing: https://github.com/mapbox/mapbox-navigation-android/pull/7582
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
Start by reviewing PR #7582 and the linked CircleCI and GitHub Actions runs for release-workflow, default, process, and publisher-deployer. Determine why optional checks were unsuccessful or skipped while the PR merged; done means the relevant merge checks enforce the documented success requirement.
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
- 25/100