[aayushshah15]

When another job is already hydrating the git mirror, checkout falls back to a direct clone from GitHub. That's expected and harmless, but the two messages were emitted with core.warning, so they appeared as warning annotations in the run summary and made customers think something was broken.

The messages still go to the step log. They just aren't annotations anymore:

if (error instanceof ConnectError && error.code === Code.Aborted) {
  // ...
  core.info(
    `[git-mirror] Another job is hydrating the git mirror cache: ${hydrationMessage}`
  )
  core.info(
    '[git-mirror] No sticky disk will be mounted for this run; ...'
  )

The fallback-contention telemetry is unchanged. dist/index.js has the same edit applied.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled. (Staging)}

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

---

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.