Summary of the new feature/enhancement

Back in Powershell 5, I could write a script which contained:

> $cred = Get-Credential -UserName "$first.$last"

A dialog would then appear, asking for the password, but it also gave the option of changing what the username was. This was useful as you could implement a naming standard, but when there was an edge case allowed the end

Thanks a ton for any helpful feedback

I need help with getting best quality GIFs.

I am not used to CSS syntax so it would be amazing if you add a lot of example config.yml files. Also, try adding config.yml files for the GIFs you are displaying in your README.md. They look fantastic. I have spent hours trying to get perfect GIF but no luck.

I don't know what value to give for shadow

Feature Request

Is your feature request related to a problem? Please describe.

I realized that starship has no documentation in Portuguese (Brazil), so I would like to contribute with project and add pt_BR translation.

Describe the solution you'd like

Documentation in Portuguese (Brazil).

Contributing

If you are interested in contributing, please take a look

The following are produced by choco.exe, thus this isn't in documentation issues. All referenced output is via Chocolatey v0.10.15

Commands
 * install - installs packages from various sources

ENHANCEMENT: "various sources" just seems misleading. What percentage of free or commercial users actually install packages from multiple sources? I'd guess most use one source or two sources;

The instructions say that you can open the file with a right click to open with powershell. However, this doesnt grant admin rights and things dont work properly. Is it possible to right click and open with powershell with admin rights?

System Details

• posh-git version/path: 1.0.0 beta4 ~\Documents\PowerShell\Modules\posh-git\1.0.0
• PowerShell version: 6.2.4
• git version 2.25.0.windows.1
• OS: Microsoft Windows NT 10.0.19041.0

The database schema is a work in progress and changes rapidly as new features get implemented or removed. Should add a check to make sure the current db file has the right schema to avoid issues like #146 .

Would you consider opening a public Wiki under this project to help document the effect of each option has in Windows? Most of the function names are pretty self-explanatory but I think Wiki with some screenshots could help remove any doubt.

Thanks for creating this!

Given this command

git commit -m "commit message" //became  git commit    "commit message"
git config --list // become git config

It would be nice to start building Pester on PowerShell 7 as well to see if it is compatible and keep it that way. To achieve that we need to research on which build servers v7 is already available. Right now we are building on TravisCI (Linux and MacOS), on AppVeyor (PowerShell 4+) and AzureDevOps (PowerShell 2&3).

Not sure if the build task needs to run on all three platforms, but it would be

today on my RSS Feed I found this great article do you think is a good idea to add it on the best practice?

We have a switch as [switch]$Enable that should enable the login but it is not actually coded to do anything.

All that is needed would be logic around whether the parameter was passed in, within the process block would be sufficient: Test-Bound Enable will return true if the parameter was properly passed into the function call.

If passed in then the login object has a Enable() method t

https://pkisharp.github.io/ACMESharp-docs/User-Guide.html

Indicates that the ACME Vault is to be initialized with the function Initialize-ACMESharp which PowerShell complains doesn't exist. After some googling around and head scratching I discover the quick start guide lists a different function Initialize-ACMEVault. That works and I was able to continue setting up ACMESharp. We get the doc

Now this has some config details in the installation docs but it would be good to have say for the 3 most popular versions PowerShell: 5.1, 6.x and 7.x some notes on:

• settings.json

• C:\Users[User}\Documents\WindowsPowerShell\Microsoft.VSCode_profile.ps1

• experimental s

Description

The use of license keys seems to be configured where it is only going to use the evaluation keys. That may be suitable for most but for those of us with MSDN licenses, or volume licenses with our employer, there is a need to use a customized key for the OS installations.

Right now this is where I find how the keys are managed:

https://github.com/AutomatedLab/AutomatedLab/bl

Documentation Issue

Pending PowerShell/PowerShell#12135
Update Tee-Object cmdlet documentation