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.

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

uv init discovers workspace from the target path #5250

Merged
merged 2 commits into from
Jul 22, 2024

Conversation

j178
Copy link
Contributor

@j178 j178 commented Jul 20, 2024

Summary

Resolves #5249

Test Plan

@j178 j178 marked this pull request as ready for review July 20, 2024 16:08
@eth3lbert
Copy link
Contributor

It would also be great to have an argument (perhaps leveraging the global isolated option) that allows us to disable workspace discovery when we don't want to add a project as a member.

Copy link
Member

@konstin konstin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@konstin konstin merged commit 178300d into astral-sh:main Jul 22, 2024
54 checks passed
@j178 j178 deleted the uv-init-outside branch July 22, 2024 14:21
charliermarsh pushed a commit that referenced this pull request Jul 22, 2024
## Summary

Per #5250 (comment)

> It would also be great to have an argument (perhaps leveraging the
global isolated option) that allows us to disable workspace discovery
when we don't want to add a project as a member.


## Test Plan

```sh

$cargo run -- init work
$ cargo run -- init work/pkg-a --isolated
warning: `uv init` is experimental and may change without warning
Initialized project sub-c in /tmp/work
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

uv init should discover workspace from the target path
3 participants