Skip to content

Conversation

@anthonykim1
Copy link
Contributor

@anthonykim1 anthonykim1 commented Dec 3, 2025

Resolves: #1000

Fix regression to allow cmd to work again with shell startup.
Also make sure to switch activation method to command if user declines modification (if applicable) when trying to switch to shell startup.

Should add tests covering various scenarios with #1019

@anthonykim1 anthonykim1 self-assigned this Dec 3, 2025
@anthonykim1 anthonykim1 added the bug Issue identified by VS Code Team member as probable bug label Dec 3, 2025
@anthonykim1 anthonykim1 marked this pull request as ready for review December 3, 2025 07:44
@anthonykim1 anthonykim1 enabled auto-merge (squash) December 3, 2025 07:45
@vs-code-engineering vs-code-engineering bot added this to the November 2025 milestone Dec 3, 2025
@anthonykim1 anthonykim1 changed the title ShellStartup autoActivation on CMD does not work Fix regression where shell startup auto activation does not work on cmd Dec 3, 2025
@anthonykim1 anthonykim1 merged commit dfdf29f into main Dec 3, 2025
11 checks passed
@anthonykim1 anthonykim1 deleted the anthonykim1/cmdRegressionFix12/2 branch December 3, 2025 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Environment activation is not working reliably with "Command Prompt"

3 participants