ta
TanStack
GitHub
intent
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
intent
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
intent
Workspace
Succeeded
fix-windows-tests
4c4a9f6b fix: make maintainer commands and the unit suite work on Windows After rebasing onto the maintainer CLI work, 18 more tests failed on Windows. Root causes: - `git rev-parse --show-toplevel` prints forward slashes on Windows, while everything derived with node:path uses backslashes. The maintainer project root and the review root are now normalized with `resolve`, which fixes `intent maintainer add` rejecting every skill path ("must belong to the selected package") on Windows. - Maintainer output and `maintainer status --json` printed some repository-relative paths with backslashes; they now use forward slashes consistently like the rest of the maintainer code. - The focused `intent meta` test expected platform separators in rewritten link destinations, which are always forward slashes. - The review fixture inherited the developer's global excludes file, which can ignore CLAUDE.md; it now pins core.excludesFile.
by Sarah Gerrard
S
Failed
fix-windows-tests
22cac7f1 fix: make maintainer commands and the unit suite work on Windows After rebasing onto the maintainer CLI work, 18 more tests failed on Windows. Root causes: - `git rev-parse --show-toplevel` prints forward slashes on Windows, while everything derived with node:path uses backslashes. The maintainer project root and the review root are now normalized with `resolve`, which fixes `intent maintainer add` rejecting every skill path ("must belong to the selected package") on Windows. - Maintainer output and `maintainer status --json` printed some repository-relative paths with backslashes; they now use forward slashes consistently like the rest of the maintainer code. - The focused `intent meta` test expected platform separators in rewritten link destinations, which are always forward slashes. - The review fixture inherited the developer's global excludes file, which can ignore CLAUDE.md; it now pins core.excludesFile.
by Sarah Gerrard
S
Succeeded
fix-windows-tests
0783193c fix: make maintainer commands and the unit suite work on Windows After rebasing onto the maintainer CLI work, 18 more tests failed on Windows. Root causes: - `git rev-parse --show-toplevel` prints forward slashes on Windows, while everything derived with node:path uses backslashes. The maintainer project root and the review root are now normalized with `resolve`, which fixes `intent maintainer add` rejecting every skill path ("must belong to the selected package") on Windows. - Maintainer output and `maintainer status --json` printed some repository-relative paths with backslashes; they now use forward slashes consistently like the rest of the maintainer code. - The focused `intent meta` test expected platform separators in rewritten link destinations, which are always forward slashes. - The review fixture inherited the developer's global excludes file, which can ignore CLAUDE.md; it now pins core.excludesFile. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
by Sarah Gerrard
S
Previous
Next