Noor ul ain dbefc66acb fix(git-ext): honor explicit -Number 0 in PowerShell branch creation (#3412) ...

`-Number` defaults to 0, so the previous `-eq 0` / `-ne 0` checks could
not distinguish an unset flag from an explicit `-Number 0`: a user
requesting branch `000-...` was silently routed into auto-detection.
Switch both checks to `$PSBoundParameters.ContainsKey('Number')`, which
tests whether the flag was actually supplied — mirroring the bash twin's
empty-string sentinel (`[ -z "$BRANCH_NUMBER" ]` / `[ -n ... ]`).

Add a parity regression test to both TestCreateFeatureBash and
TestCreateFeaturePowerShell asserting `--number 0` / `-Number 0` yields
`000-zero`.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-10 07:45:09 -05:00

..

auto-commit.ps1

fix: PS 5.1 compat — replace non-ASCII chars in shipped PowerShell scripts (#2709)

2026-05-26 13:18:34 -05:00

create-new-feature-branch.ps1

fix(git-ext): honor explicit -Number 0 in PowerShell branch creation (#3412)

2026-07-10 07:45:09 -05:00

git-common.ps1

Support namespaced git feature branch templates (#3293)

2026-07-06 15:41:58 -05:00

initialize-repo.ps1

fix: PS 5.1 compat — replace non-ASCII chars in shipped PowerShell scripts (#2709)

2026-05-26 13:18:34 -05:00