hive-c0re: fix two more comments with the same stale repo-created-after-spawn premise
This commit is contained in:
parent
e5a9703e00
commit
7d80f5146d
2 changed files with 11 additions and 7 deletions
|
|
@ -23,9 +23,11 @@ use super::git::{
|
|||
/// avoided: whichever wrote second would win, and neither knows about
|
||||
/// the other.
|
||||
///
|
||||
/// The template ([`seed_template`]) is what the hive-level create flow
|
||||
/// still lands on, since that flow creates the forge repo *after* the
|
||||
/// first spawn.
|
||||
/// The template ([`seed_template`]) is what this still falls back to when
|
||||
/// there's genuinely nothing to clone yet — `swarm-controller` creates
|
||||
/// `agent-configs/<name>` before telling a hive to deploy, but hasn't
|
||||
/// necessarily pushed `main` to it yet, or the forge is unreachable, or
|
||||
/// the core token isn't minted.
|
||||
///
|
||||
/// **Seeding is the whole of hive-c0re's write.** Changes to the repo
|
||||
/// arrive as PRs from a clone, via the forge, like any other code
|
||||
|
|
|
|||
Loading…
Reference in a new issue