From a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Tue, 26 Nov 2024 07:48:30 +0000 Subject: refactor: err msgs 'cannot' > 'failed to' in nearly all cases 'cannot' was used when an action was tried and failed. 'failed to' is strictly better because: * just because the action didn't work that time doesnt mean it cannot work * it is better at drawing the users attention to a problem --- test_utils/src/git.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test_utils/src/git.rs') diff --git a/test_utils/src/git.rs b/test_utils/src/git.rs index 470cd83..2562799 100644 --- a/test_utils/src/git.rs +++ b/test_utils/src/git.rs @@ -265,7 +265,7 @@ impl GitTestRepo { let branch = self .git_repo .find_branch(branch_name, git2::BranchType::Local) - .context(format!("cannot find branch {branch_name}"))?; + .context(format!("failed to find branch {branch_name}"))?; Ok(branch.into_reference().peel_to_commit()?.id()) } -- cgit v1.2.3