Skip to content

Fix Windows tag checkout result handling - #114

Merged
1lck merged 3 commits into
1lck:preview/0.3.0from
yangboxuan726:fix/windows-git-tag-checkout-result
Aug 17, 2026
Merged

Fix Windows tag checkout result handling#114
1lck merged 3 commits into
1lck:preview/0.3.0from
yangboxuan726:fix/windows-git-tag-checkout-result

Conversation

@yangboxuan726

Copy link
Copy Markdown
Contributor

What changed

  • Adapt git_checkout_tag from the shared Core { output, exitCode } result instead of always reporting success.
  • Preserve trimmed Core output as the checkout message and report non-zero exits as failures.
  • Add focused frontend regression coverage for zero and non-zero exit codes.

Why

The Windows result adapter previously returned success: true for every tag checkout, so Git failures could be presented as successful and trigger a Git-changed event. The existing checkoutTag API emits only when the adapted result is successful; propagating the real exit code restores that contract.

Validation

  • bun test src/platform/core-result-adapter.test.ts (7 passed)
  • bun test src/platform (21 passed)
  • bun run typecheck
  • ./scripts/verify-windows-boundaries.ps1
  • ./scripts/build-windows.ps1 -Configuration Release
  • cargo test --manifest-path windows/tauri/src-tauri/Cargo.toml (32 passed)

@yangboxuan726
yangboxuan726 force-pushed the fix/windows-git-tag-checkout-result branch from e891db7 to 3e44fbb Compare August 16, 2026 13:53
@yangboxuan726
yangboxuan726 marked this pull request as ready for review August 17, 2026 00:35
@yangboxuan726
yangboxuan726 requested a review from 1lck as a code owner August 17, 2026 00:35
@1lck
1lck merged commit f1786c1 into 1lck:preview/0.3.0 Aug 17, 2026
5 of 6 checks passed
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.

2 participants