ci: make main the canonical branch (badges guard, docs)
Point the badges job's branch guard at refs/heads/main and update the README / ci-cd docs to name main as the canonical branch, ahead of establishing main from bringup as the SDK's first main commit. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
620a21928d
commit
4f060db1b1
@@ -13,7 +13,7 @@ what runs on real silicon versus what we simulate.
|
||||
|
||||
> Status: **bringup.** The hardware **simulator** and its tests, the RV1106 kernel
|
||||
> forward-port as a reviewable `patches/` series, the hermetic kernel build, and two
|
||||
> Tier-1 drivers at 100% MC/DC are all in and CI-green on the `bringup` branch. What
|
||||
> Tier-1 drivers at 100% MC/DC are all in and CI-green on `main`. What
|
||||
> remains before this is on the production build path: installing the self-hosted
|
||||
> kernel-build runner (see `docs/ci-cd.md`) and having flare-edge consume warden-sdk
|
||||
> as a dependency — both [maintainer]-gated. Until then, flare-edge still builds firmware from
|
||||
|
||||
Reference in New Issue
Block a user