CI: skip st-onboard-a5 while the a5 runner is under repair

[ChaoWao]

Summary

• Short-circuit the st-onboard-a5 gate to if: false && ... so the job reports skipped instead of waiting on a runner that is out for repair.
• The original condition is kept inline; re-enabling is deleting false && .

The a5 self-hosted runner is under repair, so st-onboard-a5 has no host to pick it up. Nothing declares needs: st-onboard-a5 and main has no required status checks, so skipping it blocks no merge.

Coverage for a5 changes falls back to st-sim-a5 (GitHub-hosted). ut-a5 targets the same self-hosted runner and is deliberately left enabled — if the repair runs long it will need the same treatment.

Testing

• YAML parses and the job's if resolves as intended (yaml.safe_load → false && needs.detect-changes.outputs.a5_changed == 'true')
• Simulation tests pass — n/a, CI config only
• Hardware tests pass — n/a (and a5 hardware is the thing under repair)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 898d7c90-d3a3-43ab-9e39-1a9edd41ef9d

📥 Commits

Reviewing files that changed from the base of the PR and between ae2611d and 1a178ab.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

---

📝 Walkthrough

Walkthrough

The st-onboard-a5 CI job is forcibly disabled by adding a false && guard to its execution condition while its self-hosted runner is under repair.

Changes

CI runner maintenance

Layer / File(s)	Summary
Disable a5 onboarding job .github/workflows/ci.yml	The st-onboard-a5 job now remains disabled regardless of the a5_changed output, with a comment noting the runner repair.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

I’m a rabbit with a wrench in sight,
Pausing a runner through the night.
The a5 job rests, its guard says “no,”
Till repaired runners make it go.
Hop, hop—CI waits below!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main CI change and why the job is being skipped.
Description check	✅ Passed	The description is directly related to the CI workflow change and explains the skip behavior and rationale.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}