mapbox / mapbox/mapbox-navigation-android
PR #7396 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
👋 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 | Required? | Best practice guidelines |
|---|---|---|---|
| Run unsuccessful: ci/circleci: release-workflow/release-snapshot-start | pending | optional | success |
| Run unsuccessful: ci/circleci: default/mobile-metrics-dry-run | pending | optional | success |
| Run unsuccessful: process | skipped | optional | success |
| Run unsuccessful: process | skipped | optional | success |
| Run unsuccessful: publisher-deployer | neutral | optional | success |
| Run unsuccessful: release-workflow | null | optional | success |
| Run unsuccessful: default | null | optional | success |
The following PR was merged without the status checks passing: https://github.com/mapbox/mapbox-navigation-android/pull/7396
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 merged PR #7396 and the linked CircleCI and GitHub Actions runs, including release-workflow, default, process, and publisher-deployer. Determine why optional checks were unsuccessful or skipped and adjust the relevant workflow configuration so merged pull requests have successful status checks.
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