Skip to content

Format-GitStatusSegment: match StatusString ahead/behind ordering - #43

Merged
shmuelie merged 2 commits into
mainfrom
fix/18-status-segment-order
Aug 14, 2026
Merged

Format-GitStatusSegment: match StatusString ahead/behind ordering#43
shmuelie merged 2 commits into
mainfrom
fix/18-status-segment-order

Conversation

@shmuelie

@shmuelie shmuelie commented Aug 14, 2026

Copy link
Copy Markdown
Owner

Fixes #18

Summary

  • Format-GitStatusSegment now renders diverged upstream relations as ↓behind ↑ahead, matching Get-GitStatusSummary.StatusString.
  • Ahead-only, behind-only, up-to-date, and upstream-gone relation rendering remains unchanged and covered by tests.

Validation

  • .\build\Test-Modules.ps1
  • .\build\Invoke-Tests.ps1 -Path tests\Shmuelie.Git.Tests.ps1
  • Test-PublicRepoContent not found; skipped.

shmuelie and others added 2 commits August 14, 2026 10:01
Match Format-GitStatusSegment diverged relation output to Get-GitStatusSummary.StatusString by rendering behind before ahead with a separating space.

Add regression coverage for diverged, ahead-only, behind-only, up-to-date, and upstream-gone relation rendering.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 18be4b78-3a83-4cb1-8f77-0b837e1c3076
…-order

# Conflicts:
#	modules/Shmuelie.Git/CHANGELOG.md
@shmuelie
shmuelie merged commit 3f4af40 into main Aug 14, 2026
@shmuelie
shmuelie deleted the fix/18-status-segment-order branch August 14, 2026 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Format-GitStatusSegment ahead/behind relation is inconsistent with Get-GitStatusSummary.StatusString (↑A↓B vs ↓B ↑A)

1 participant