diff tests/test-rename-rev.t @ 48247:c62e4397eb28

copy: recommend `--at-rev .` if target was added in parent commit

If the target file was added in the working copy parent, it's much
more likely that the user meant to use `--at-rev .` (to record the
copy/rename in the that commit) than `--force` (to replace the
just-added file by another file).

Differential Revision: https://phab.mercurial-scm.org/D11667

--- a/tests/test-rename-rev.t	Mon Oct 18 10:14:44 2021 +0200
+++ b/tests/test-rename-rev.t	Thu Oct 14 10:58:39 2021 -0700
@@ -42,6 +42,17 @@
     d1/b
   A d1/d
     d1/b
+# Should get helpful message if we try to copy or rename after commit
+  $ hg cp --forget --at-rev . d1/d
+  saved backup bundle to $TESTTMP/.hg/strip-backup/3f7c325d3f9e-46f377bb-uncopy.hg
+  $ hg cp d1/b d1/d
+  d1/d: not overwriting - file already committed
+  ('hg copy --at-rev .' to record the copy in the parent of the working copy)
+  [1]
+  $ hg mv d1/b d1/d
+  d1/d: not overwriting - file already committed
+  ('hg rename --at-rev .' to record the rename in the parent of the working copy)
+  [1]
 
 Test moved file (not copied) using 'hg cp' command