the rendered meta flake pins each agent config by forge URL at its forge main
This commit is contained in:
parent
fc72bea151
commit
09cabf8398
8 changed files with 432 additions and 163 deletions
|
|
@ -11,6 +11,7 @@ mod repos;
|
|||
mod users;
|
||||
|
||||
pub use reader::reader_token;
|
||||
pub(crate) use reconcile::FORGE_MAIN_REF;
|
||||
pub use reconcile::{fetch_forge_main, reconcile_config_apply, reconcile_config_status};
|
||||
pub use repos::{
|
||||
clone_config_into_proposed, ensure_meta_remote, ensure_repo, fast_forward_applied_main,
|
||||
|
|
|
|||
|
|
@ -6,9 +6,8 @@
|
|||
//!
|
||||
//! `Status` is read-only (fetches forge `main` into a scratch ref, reports
|
||||
//! the divergence). `Apply(Forge)` resets the local applied checkout to
|
||||
//! forge `main` — the change takes effect on the next deploy (the deploy's
|
||||
//! `--override-input` re-locks against the reset local tree); it does NOT
|
||||
//! auto-deploy. `Apply(Local)` is not supported: forge `main` is
|
||||
//! forge `main`; the meta flake pins forge `main` itself, not this tree. It
|
||||
//! does NOT auto-deploy. `Apply(Local)` is not supported: forge `main` is
|
||||
//! branch-protected, so it only advances through a config-PR merge.
|
||||
|
||||
use std::path::{Path, PathBuf};
|
||||
|
|
@ -21,7 +20,7 @@ use super::{CONFIG_ORG, forge_git_url, reader_token};
|
|||
|
||||
/// Scratch ref the forge `main` is fetched into — outside the normal
|
||||
/// branch/tag namespace so it never collides with real refs.
|
||||
const FORGE_MAIN_REF: &str = "refs/hyperhive/forge-config-main";
|
||||
pub(crate) const FORGE_MAIN_REF: &str = "refs/hyperhive/forge-config-main";
|
||||
|
||||
/// Fetch `agent-configs/<agent>` `main` into the applied repo's scratch
|
||||
/// ref (read-only, no working-tree change) and return the applied dir.
|
||||
|
|
|
|||
Loading…
Reference in a new issue