Skip to content

correct workspace path for mutiroot scenarios no-config debugging #602

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

Merged
merged 2 commits into from
Feb 11, 2025

Conversation

eleanorjboyd
Copy link
Member

No description provided.

Copy link

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

@eleanorjboyd eleanorjboyd merged commit 020cc10 into microsoft:main Feb 11, 2025
16 checks passed
@eleanorjboyd eleanorjboyd deleted the fix-workspace-path branch February 11, 2025 19:08
eleanorjboyd added a commit to eleanorjboyd/vscode-python-debugger that referenced this pull request Feb 11, 2025
…crosoft#602)

* correct workspace path for mutiroot scenarios no-config debugging

* rename
eleanorjboyd added a commit that referenced this pull request Feb 11, 2025
…) (#607)

* correct workspace path for mutiroot scenarios no-config debugging

* rename
eleanorjboyd added a commit to eleanorjboyd/vscode-python-debugger that referenced this pull request Feb 12, 2025
…crosoft#602)

* correct workspace path for mutiroot scenarios no-config debugging

* rename
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants