Sometimes I use cargo new to build a sub-package inside another package (useful for macros for example), but cargo new automatically creates a new git repo even if you are already in a Cargo project with a git repo.
Yeah, just not doing it is a better default than making you --no-git
Most helpful comment
Yeah, just not doing it is a better default than making you
--no-git