From 49998341b4ea0de3dba959223ee4a7da8da45115 Mon Sep 17 00:00:00 2001 From: David Sherret Date: Fri, 8 Mar 2024 17:49:15 -0500 Subject: [PATCH] fix(publish): suggest using `--allow-dirty` on uncommitted changes (#22810) --- cli/tools/registry/mod.rs | 2 +- tests/integration/publish_tests.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/cli/tools/registry/mod.rs b/cli/tools/registry/mod.rs index f8c79d85c5..f3321e44a2 100644 --- a/cli/tools/registry/mod.rs +++ b/cli/tools/registry/mod.rs @@ -952,7 +952,7 @@ pub async fn publish( && !publish_flags.allow_dirty && check_if_git_repo_dirty(cli_options.initial_cwd()).await { - bail!("Aborting due to uncomitted changes",); + bail!("Aborting due to uncommitted changes. Check in source code or run with --allow-dirty"); } perform_publish( diff --git a/tests/integration/publish_tests.rs b/tests/integration/publish_tests.rs index 49c531e7da..a590e02ad5 100644 --- a/tests/integration/publish_tests.rs +++ b/tests/integration/publish_tests.rs @@ -630,7 +630,7 @@ fn allow_dirty() { .run(); output.assert_exit_code(1); let output = output.combined_output(); - assert_contains!(output, "Aborting due to uncomitted changes"); + assert_contains!(output, "Aborting due to uncommitted changes. Check in source code or run with --allow-dirty"); let output = context .new_command()