hive-c0re: stop mirroring deploy tags to the forge (drop push_config)
Per the operator's ruling on #4851 (option (a)): the hive holds no write identity on the forge, so the `push_config` mirror of an applied repo's tags and `main` to `agent-configs/<name>` is removed, along with its `run_config_push` helper and its call in `sync_agent`. Docs and comments that described the mirror now say that forge `main` advances only by an operator's merge. Refs #4851
This commit is contained in:
parent
c1672218b1
commit
456a4511ab
6 changed files with 33 additions and 137 deletions
|
|
@ -98,9 +98,8 @@ pub async fn pull(coord: &Coordinator) -> Result<()> {
|
|||
}
|
||||
// Rewrite any credentialed `origin` left by an older clone, which spliced
|
||||
// `core:<token>@` into the URL and persisted it in `.git/config` — the one
|
||||
// place this repo stored a token in a named remote, against the rule
|
||||
// `forge::repos::push_config` states. Harmless to repeat once the URL is
|
||||
// already clean.
|
||||
// place this repo stored a token in a named remote. Harmless to repeat
|
||||
// once the URL is already clean.
|
||||
let plain = crate::forge::forge_git_url(&format!("{ORG}/{REPO}"));
|
||||
let _ = crate::lifecycle::git_command()
|
||||
.args(["-C", LOCAL_DIR, "remote", "set-url", "origin", &plain])
|
||||
|
|
|
|||
Loading…
Reference in a new issue