rebase: ignore untracked files in submodules
An untracked file in a submodule should not prevent a rebase from starting. Even if the submodule's SHA is changed, and that file would conflict with a new tracked file, it's still OK to start the rebase and discover the conflict later. Signed-off-by: David Turner <dturner@twosigma.com>
Showing
tests/rebase/submodule.c
0 → 100644
tests/resources/rebase-submodule/.gitmodules
0 → 100644
File added
File added
File added
File added
File added
File added
File added
File added
File added
File added
File added
File added
File added
File added
File added
tests/resources/rebase-submodule/beef.txt
0 → 100644
tests/resources/rebase-submodule/bouilli.txt
0 → 100644
tests/resources/rebase-submodule/gravy.txt
0 → 100644
my-submodule @ efad0b11
tests/resources/rebase-submodule/oyster.txt
0 → 100644
tests/resources/rebase-submodule/veal.txt
0 → 100644
Please
register
or
sign in
to comment