CircleCI-Public / CircleCI-Public/windows-preview-docs
powershell always runs with --NoProfile
- Dominant language
- No language data
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
powershell gets always invoked with `-NoProfile` option. This makes persisting PATH and other changes, say, after installing packages with Chocolatey, very difficult (have to repeatedly re-set PATH or run a set-up script for every `run`, instead of saving everything needed to a script that would get run by the profile mechanism)
Do you think this can be changed, or allowed to be changed in shell spec per job?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how PowerShell is invoked with `-NoProfile` and how the shell spec per job is documented in this repository. Determine whether profile loading can be enabled or configured, then document the supported behavior and verify the example matches the Windows build setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100