Hmmm, I think you're right. That's less dangerous, especially when people don't really know what they're doing. I'll push an update. That said . should be spec

Hmmm, I think you're right. That's less dangerous, especially when people don't really know what they're doing. I'll push an update. That said . should be specified per manpages: > If no <pathspec> is given, the current version of Git defaults to "."; in other words, update all files in the current directory and its subdirectories. This default will change in a future version of Git, hence the form without <pathspec> should not be used.