This sounds like a great enhancement 👍

It was always interesting how only Get-ChildItem had a -Hidden parameter which only displayed hidden files. If you also wanted non-hidden files you would also need to use -Force.

Makes sense to use -Force for consistency to include hidden files for all cmdlets.

I noticed as well on Ubuntu this seems to only be an issue with wildcards:

12-21 18:37:36 ~/git-repos/PowerShell [master ≡]> Convert-Path ./.gitignore
/home/armaan/git-repos/PowerShell/.gitignore
12-21 18:37:52 ~/git-repos/PowerShell [master ≡]> Convert-Path ./.git*
12-21 18:37:55 ~/git-repos/PowerShell [master ≡]>
12-21 18:37:55 ~/git-repos/PowerShell [master ≡]> Resolve-Path ./.gitignore

Path
----
/home/jdoe/git-repos/PowerShell/.gitignore

12-21 18:40:39 ~/git-repos/PowerShell [master ≡]> Resolve-Path ./.git*
12-21 18:40:42 ~/git-repos/PowerShell [master ≡]>

On Windows it works as expected:

12-21 18:39:15 ~\git-repos\PowerShell [master ≡]> Convert-Path .\.gitignore
C:\Users\jdoe\git-repos\PowerShell\.gitignore
12-21 18:39:20 ~\git-repos\PowerShell [master ≡]> Convert-Path .\.git*
C:\Users\jdoe\git-repos\PowerShell\.github
C:\Users\jdoe\git-repos\PowerShell\.gitattributes
C:\Users\jdoe\git-repos\PowerShell\.gitignore
12-21 18:39:23 ~\git-repos\PowerShell [master ≡]> Resolve-Path .\.gitignore

Path
----
C:\Users\jdoe\git-repos\PowerShell\.gitignore

12-21 18:40:05 ~\git-repos\PowerShell [master ≡]> Resolve-Path .\.git*

Path
----
C:\Users\jdoe\git-repos\PowerShell\.github
C:\Users\jdoe\git-repos\PowerShell\.gitattributes
C:\Users\jdoe\git-repos\PowerShell\.gitignore

Thanks, @ArmaanMcleod.

Good point about only wildcard expressions being affected (I've updated the initial post to clarify.)

Note that .-prefixed files aren't necessarily hidden on Windows, which explains why even wildcard-based matching found it. There, it is the Hidden attribute that matters, so if you hide, say, .\.gitignore with attrib -h .\.gitignore, Convert-Path .\.git* will no longer match it.

As an aside:

• The distinction between literal paths and wildcard-based matching with respect to hidden items generally makes sense - but, unfortunately, isn't observed by Get-Item and Get-ChildItem
• See Get-Item and Get-ChildItem, unlike the other filesystem-provider cmdlets, require -Force to target hidden items with literal paths #6502

I forgot that years ago I had asked for the same, only more comprehensively:

• Test-Path, Split-Path -Resolve, Join-Path -Resolve, and Invoke-Item too need a -Force switch in order to include hidden items when using wildcards - see Add a -Force switch to Test-Path, Convert-Path, Resolve-Path, Split-Path -Resolve, Join-Path -Resolve, Invoke-Item for targeting hidden items #6501.