You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to understand whether cargo's behavior when creating a new project inside a git repo is working as intended. When creating a new project at the top level of an existing repo, it does not initialize a new git repo within the created project. However, when initializing a new project deep within an existing git repo, e.g., cargo new deep/path/to/project, a new git repo will be initialized despite the project being inside an already existing git repo.
Steps
# create in project at root of git repocd /repo
git init # creates /repo/.git
cargo new foo # no git repo created inside /repo/foo# create project in subdir of git repocd /repo2
git init # creates /repo2/.git
cargo new foo/bar/baz # initializes new git repo at /repo2/foo/bar/baz/.git
Possible Solution(s)
If this behavior is intended, perhaps doc update will be enough?
Notes
No response
Version
cargo 1.68.2 (6feb7c9cf 2023-03-26)
The text was updated successfully, but these errors were encountered:
Problem
I'm trying to understand whether cargo's behavior when creating a new project inside a git repo is working as intended. When creating a new project at the top level of an existing repo, it does not initialize a new git repo within the created project. However, when initializing a new project deep within an existing git repo, e.g.,
cargo new deep/path/to/project
, a new git repo will be initialized despite the project being inside an already existing git repo.Steps
Possible Solution(s)
If this behavior is intended, perhaps doc update will be enough?
Notes
No response
Version
The text was updated successfully, but these errors were encountered: