You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,16 @@
5
5
1. Take the desired configuration scripts from the [winget_configurations folder](./winget_configurations)
6
6
2. Follow the instructions at [https://learn.microsoft.com/windows/package-manager/configuration/](https://learn.microsoft.com/windows/package-manager/configuration/?WT.mc_id=8B97120A00B57354#use-a-winget-configuration-file-to-configure-your-machine) to setup your machine
7
7
8
+
## Running install.ps1
9
+
10
+
On a fresh Windows machine the default execution policy is **Restricted**, which prevents PowerShell from running `.ps1` scripts entirely. The in-script execution-policy check (`Set-ExecutionPolicy Bypass -Scope Process`) is a safety notice only — it cannot bootstrap itself from Restricted mode because the script never gets to execute.
#/NoAutoCrlf" <# This setting only affects new installs, it will not override an existing .gitconfig. This will ensure 'Checkout as is, commit as is' #>
22
22
}
23
23
24
-
Install-Module posh-git -y -Scope -AllUsers -force -allowclobber# Both Posh-Git and IntelliTect.Git support Get-GitBranch.
24
+
Install-Module posh-git -Scope AllUsers -Force -AllowClobber# Both Posh-Git and IntelliTect.Git support Get-GitBranch.
25
25
# IntelliTect.Git will get priority if it appears first in the PSModulePath
26
26
# or it is installed after Pscx (if not using source code)
0 commit comments