1GIT-MV(1)                         Git Manual                         GIT-MV(1)
2
3
4

NAME

6       git-mv - Move or rename a file, a directory, or a symlink
7

SYNOPSIS

9       git mv <options>... <args>...
10

DESCRIPTION

12       Move or rename a file, directory or symlink.
13
14           git mv [-v] [-f] [-n] [-k] <source> <destination>
15           git mv [-v] [-f] [-n] [-k] <source> ... <destination directory>
16
17       In the first form, it renames <source>, which must exist and be either
18       a file, symlink or directory, to <destination>. In the second form, the
19       last argument has to be an existing directory; the given sources will
20       be moved into this directory.
21
22       The index is updated after successful completion, but the change must
23       still be committed.
24

OPTIONS

26       -f, --force
27           Force renaming or moving of a file even if the target exists
28
29       -k
30           Skip move or rename actions which would lead to an error condition.
31           An error happens when a source is neither existing nor controlled
32           by Git, or when it would overwrite an existing file unless -f is
33           given.
34
35       -n, --dry-run
36           Do nothing; only show what would happen
37
38       -v, --verbose
39           Report the names of files as they are moved.
40

SUBMODULES

42       Moving a submodule using a gitfile (which means they were cloned with a
43       Git version 1.7.8 or newer) will update the gitfile and core.worktree
44       setting to make the submodule work in the new location. It also will
45       attempt to update the submodule.<name>.path setting in the
46       gitmodules(5) file and stage that file (unless -n is used).
47

BUGS

49       Each time a superproject update moves a populated submodule (e.g. when
50       switching between commits before and after the move) a stale submodule
51       checkout will remain in the old location and an empty directory will
52       appear in the new location. To populate the submodule again in the new
53       location the user will have to run "git submodule update" afterwards.
54       Removing the old directory is only safe when it uses a gitfile, as
55       otherwise the history of the submodule will be deleted too. Both steps
56       will be obsolete when recursive submodule update has been implemented.
57

GIT

59       Part of the git(1) suite
60
61
62
63Git 2.33.1                        2021-10-12                         GIT-MV(1)
Impressum