Skip to content

test(core): expect the vcs provider in info results - #49264

Merged
thdxr merged 1 commit into
v2from
fix-vcs-tests
Sep 16, 2026
Merged

thdxr merged 1 commit into
v2from
fix-vcs-tests

Conversation

@thdxr

@thdxr thdxr commented Sep 16, 2026

Copy link
Copy Markdown
Member

Issue for this PR

Closes # — no issue; fixes CI for every core PR.

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

b1f6d21 (refactor(protocol): refine vcs and shell APIs) added the selected provider's ID to Vcs.info() results and updated the TUI diff-viewer test, but not packages/core/test/vcs.test.ts or vcs-hg.test.ts. v2 CI stayed green because the affected-package filter did not rerun core tests for that push, so the seven stale toEqual expectations only surface on PRs that touch core (for example #49255). This updates those expectations to include provider: "custom" | "git" | "hg" to match the current implementation. No source changes.

How did you verify your code works?

cd packages/core && bun test test/vcs.test.ts test/vcs-hg.test.ts: 35 pass, 0 fail (the mercurial cases skip locally without hg; CI runs them). Lint clean.

Screenshots / recordings

Not a UI change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

from OpenCode

b1f6d21 added the selected provider's ID to Vcs.info() without
updating the core Vcs tests, which CI did not run for that push.
@thdxr
thdxr merged commit a062f4e into v2 Sep 16, 2026
10 checks passed
@thdxr
thdxr deleted the fix-vcs-tests branch September 16, 2026 03:01
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.

1 participant