jdx/mise · error
this machine is connected to {url}; `mise bootstrap dotfiles
Error message
this machine is connected to {url}; `mise bootstrap dotfiles origin --remove` disconnects it, or `mise bootstrap dotfiles origin set {origin}` moves it What it means
Safety bail in refuse_other_connection: this machine's history status is already connected to a different repository URL than the one requested, and onboarding never silently repoints a machine to a new repository. The error names both remediation commands (disconnect or set a new origin).
Source
Thrown at src/system/history/sync/onboard.rs:204
if refs.iter().any(|(_, name)| name == candidate) {
return Ok(Some(
candidate.trim_start_matches("refs/heads/").to_string(),
));
}
}
Ok(refs
.iter()
.find_map(|(_, name)| name.strip_prefix("refs/heads/").map(str::to_string)))
}
/// A machine connected to another repository is not silently moved.
fn refuse_other_connection(store: &Store, origin: &str, branch: &str) -> Result<()> {
let status = run::read_status(store.state_dir())?;
if let Some(url) = &status.origin_url
&& !status.disconnected
&& (url != origin || status.origin_branch.as_deref() != Some(branch))
{
bail!(
"this machine is connected to {url}; `mise bootstrap dotfiles origin --remove` disconnects it, or `mise bootstrap dotfiles origin set {origin}` moves it"
);
}
Ok(())
}
/// Fetches the branch into the store and says what the repository is. A
/// format this mise does not understand is an error; an ordinary
/// repository leaves nothing behind.
fn probe(store: &Store, fetch_from: &str, branch: &str) -> Result<RepoState> {
let repo = store
.repo()
.ok_or_else(|| eyre::eyre!("probing a setup repository requires git"))?;
Remote::new(repo, fetch_from).fetch_tip(branch)?;
let upstream = repo.ref_oid(UPSTREAM_REF)?;
let state = format::detect(repo, upstream.as_deref())?;
state.check()?;
if !matches!(state, RepoState::Marked(_)) && upstream.is_some() {View on GitHub (pinned to afd2eddd3a)
Solutions
- Run `mise bootstrap dotfiles origin --remove` to disconnect from the current repository first
- Or run `mise bootstrap dotfiles origin set <new-url>` to move the connection deliberately
- Then re-run onboarding against the intended repository
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/system/history/sync/onboard.rs:204 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of jdx/mise@afd2eddd3a (2026-09-09).
Data as JSON: /api/errors/da3c21fb08fbdca0.
Report an issue: GitHub.