Skip to content

bug fix: enhance conda environment management with sourcing status and updated shell activation support #693

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

eleanorjboyd
Copy link
Member

No description provided.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR enhances conda environment management by adding sourcing status detection and improving shell activation support. The changes introduce a new system to determine whether conda is already active in the current shell and provide better shell-specific activation commands.

  • Adds CondaSourcingStatus class to track conda initialization state
  • Refactors shell activation command generation to use sourcing information
  • Introduces detection of global and shell-specific conda activation scripts

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.

File Description
src/managers/conda/main.ts Adds sourcing status construction and assignment to environment manager
src/managers/conda/condaUtils.ts Refactors shell activation logic to use sourcing status and removes duplicate code
src/managers/conda/condaSourcingUtils.ts New utility for detecting conda sourcing status and activation scripts
src/managers/conda/condaEnvManager.ts Adds sourcingInformation property to store sourcing status

@eleanorjboyd eleanorjboyd marked this pull request as ready for review August 8, 2025 20:21
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.

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.

1 participant