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

Add .code-workspace example for "Mono Repo Set‐up Guide" - "Separate Virtual Environments" scenario #22595

Open
tibbe opened this issue Dec 6, 2023 · 2 comments
Assignees
Labels
area-editor-* User-facing catch-all documentation feature-request Request for new features or functionality needs PR Ready to be worked on

Comments

@tibbe
Copy link

tibbe commented Dec 6, 2023

In the Mono Repo Set‐up Guide in "Scenario 2: Separate Virtual Environments" there's a link to the Responsible AI Toolbox repo, as an example of a monorepo using a multi-root workspace. However, there's no .code-workspace file in the example repo, suggesting that this is not in fact an example of a multi-root workspace.

Perhaps the repo changed since it was introduced as an example.

/cc @luabud

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Dec 6, 2023
@luabud
Copy link
Member

luabud commented Dec 13, 2023

Thanks for bringing this up! I meant to link it as an example of a repo that could be set up as multi-root workspace, but the wording is currently confusing indeed. I'll update it to make that clearer and will see if it'd be helpful to include an example of what .code-workspace would look like if one followed the steps there in that repo!

@luabud luabud changed the title Example linked from "Mono Repo Set‐up Guide" - "Separate Virtual Environments" doesn't seem to be a multi-root workspace Add .code-workspace example for "Mono Repo Set‐up Guide" - "Separate Virtual Environments" scenario Dec 13, 2023
@luabud luabud added area-editor-* User-facing catch-all documentation needs PR Ready to be worked on feature-request Request for new features or functionality and removed triage-needed Needs assignment to the proper sub-team labels Dec 13, 2023
@tibbe
Copy link
Author

tibbe commented Dec 14, 2023

That would be great, especially a link to a repo that actually uses a multi-root workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-editor-* User-facing catch-all documentation feature-request Request for new features or functionality needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

2 participants