Install CTT PowerShell Profile should create a new profile

[Noctran]

⚙️ Issue Checklist

• [x] I have read the guidelines.
• [x] I checked for duplicate issues.
• [x] I searched for existing discussions.
• [x] I checked for an existing pull request that addresses this request.

❓ Is your feature request related to a problem?

I'm not happy with "Install CTT PowerShell Profile", it should not overwrite/change the current Powershell Profile without at least making that very very clear!

💡 Describe the solution you'd like

The default Behaviour should be to install an additional Profile (at least a Windows Terminal Profile).

Would also suggest offering the option to clone the current profile to keep existing customizations, with the default being creating a new profile.

🔄 Describe alternatives you've considered

Add the Information in the GUI about what's going to happen, that this button means changing the normal PowerShell Profile

🖼️ Additional context

No response

[ruxunderscore]

When Chris's Powershell Profile installs, it checks for an existing profile. If the profile exists, it moves it to oldprofile.ps1. You can open that file and see your old profile's Functions, Aliases, and whatever other customizations you made. Then you can use Edit-Profile to move those implementations to your $PROFILE.CurrentUserAllHosts, which will never be overwritten, like the $PROFILE will. I would recommend checking out his powershell-profile repository and suggesting changes there.

[github-actions[bot]]

This issue was marked as stale due to inactivity.