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 --- tests/git_remote_nostr/main.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/git_remote_nostr/main.rs') diff --git a/tests/git_remote_nostr/main.rs b/tests/git_remote_nostr/main.rs index f749c7f..84e66bd 100644 --- a/tests/git_remote_nostr/main.rs +++ b/tests/git_remote_nostr/main.rs @@ -43,7 +43,7 @@ fn set_git_nostr_login_config(test_repo: &GitTestRepo) -> Result<()> { let mut config = test_repo .git_repo .config() - .context("cannot open git config")?; + .context("failed to open git config")?; config.set_str("nostr.nsec", TEST_KEY_2_NSEC)?; config.set_str("nostr.npub", TEST_KEY_2_NPUB)?; config.set_str("user.name", "test name")?; -- cgit v1.2.3