hive-c0re: fix a doc comment still naming the deleted forge_after_first_spawn
This commit is contained in:
parent
eaa26d7e1e
commit
e5a9703e00
1 changed files with 2 additions and 2 deletions
|
|
@ -432,8 +432,8 @@ pub async fn fast_forward_applied_main(name: &str) -> bool {
|
||||||
/// Best-effort like [`fetch_config_main_into_applied`], and `false` is an
|
/// Best-effort like [`fetch_config_main_into_applied`], and `false` is an
|
||||||
/// ordinary answer rather than an error: the forge is absent, the core token
|
/// ordinary answer rather than an error: the forge is absent, the core token
|
||||||
/// is not minted yet, or `agent-configs/<name>` has no `main` — the last of
|
/// is not minted yet, or `agent-configs/<name>` has no `main` — the last of
|
||||||
/// which is the *normal* case for the hive-level create flow, where the repo
|
/// which is the *normal* case right after `swarm-controller` creates the
|
||||||
/// is only created after the first spawn (`actions::forge_after_first_spawn`).
|
/// agent, before it has pushed anything into the repo it just made.
|
||||||
///
|
///
|
||||||
/// `clone` rather than `init` + `fetch`: git removes a directory it created
|
/// `clone` rather than `init` + `fetch`: git removes a directory it created
|
||||||
/// when the clone fails, and cloning into an existing empty dir leaves no
|
/// when the clone fails, and cloning into an existing empty dir leaves no
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue