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

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing PR #7859 and the listed CircleCI, GitHub Actions, and Prisma Cloud checks to determine why the merge proceeded while checks were pending, null, skipped, or neutral. Done means the relevant status checks reliably report success or prevent merging when they do not, with the behavior verified on a test pull request.

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 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: ci/circleci: assemble pending optional success
Run unsuccessful: ci/circleci: unit-tests-core pending optional success
Run unsuccessful: ci/circleci: changelog-verification pending optional success
Run unsuccessful: ci/circleci: ui-robo-tests pending optional success
Run unsuccessful: ci/circleci: unit-tests-androidauto pending optional success
Run unsuccessful: ci/circleci: assemble-instrumentation-test pending optional success
Run unsuccessful: Prisma Cloud / Code analysis pending optional success
Run unsuccessful: ci/circleci: assemble-instrumentation-test-internal pending optional success
Run unsuccessful: ci/circleci: assemble-old-deps-compat pending optional success
Run unsuccessful: ci/circleci: assemble-app-mincompile pending optional success
Run unsuccessful: ci/circleci: prepare-static-analysis pending optional success
Run unsuccessful: Analyze (python) null optional success
Run unsuccessful: Analyze (java) null optional success
Run unsuccessful: process null optional success
Run unsuccessful: process skipped optional success
Run unsuccessful: publisher-deployer neutral optional success
Run unsuccessful: default null optional success
Run unsuccessful: release-workflow null optional success

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

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
PR merge metrics
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.