Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

anchor init should consider already existing workspace #2940

Open
ranile opened this issue Apr 28, 2024 · 1 comment
Open

anchor init should consider already existing workspace #2940

ranile opened this issue Apr 28, 2024 · 1 comment
Assignees
@murluki
Labels
cli enhancement New feature or request good first issue Good for newcomers

Comments

@ranile
Copy link

ranile commented Apr 28, 2024

Cargo doesn't support nested workspaces. When anchor init is run, it unconditionally creates a new workspace and members of that workspace.

It should try to find an existing workspace. If one exists, that workspace should be used. Otherwise a new workspace should be created
@acheroncrypto acheroncrypto added enhancement New feature or request good first issue Good for newcomers cli labels Apr 29, 2024
@murluki
Copy link

murluki commented May 3, 2024

could you please assign that to me, please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@murluki murluki

Labels
cli enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ranile @acheroncrypto @murluki