I had a situation lately where I had a very very l...
# ideas
a
I had a situation lately where I had a very very large file in my repo directory that was untracked (but not gitignored). This caused the
git update-index
etc steps to take more than 7m 😅 and very much confused me as to why
gt sync
was "hanging" (not `gt`'s fault in the end at all). It would be nice if such huge files could be detected and warned about in
--debug
logs at least (even more ideally to
stderr
or something generally) so as to explain what's going on 🙂
j
Hey Avery, thanks for writing in! This issue is already on our radar, so I updated the request with your feedback: the
--debug
output should explain the likely cause, not just show the Git command. For example, it could explicitly warn when a very large untracked file is likely making Git index operations slow. In the meantime, the workaround is to move that file outside the repo or add it to
.gitignore
if it should never be tracked.