From 78974c732c000212e70d02ed2e177f68b568b3ee Mon Sep 17 00:00:00 2001 From: Scott Date: Wed, 2 Sep 2026 11:30:15 +1000 Subject: [PATCH] docs(git-provider): Update general section to outline case-sensitivity --- docs/GitRepositoryRegistration.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/GitRepositoryRegistration.md b/docs/GitRepositoryRegistration.md index 2ce24f0..8bff64e 100644 --- a/docs/GitRepositoryRegistration.md +++ b/docs/GitRepositoryRegistration.md @@ -5,7 +5,12 @@ Most `*-GitRepoRegistration` commands are expected to be run within a folder that is contained within a git repo. The only exceptions to this are any verbs that list information or change locations such as `Get-`, `Show-`, `Push-`, `Pop-`. -Any exceptions to behaviours are outlined within the relevant command section +Any exceptions to behaviours are outlined within the relevant command section. + +> [!info] Case-Sensitivity +> For all commands, the `Name` parameter is treated as _case-sensitive_, so multiple registrations can exist with the same name but different casing and point to different git repo locations or the same location - acting as an alias in a sense. +> +> While this isn't explicitly supported functionality, we don't do anything to prevent you having multiple registrations for the same git repo. Why should we after all? This set of commandlets are designed to make git repos more organised so how you use it is up to you. ## New-GitRepoRegistration