Skip to content

feat(cli): add llmwiki rm <source> (#179) #488

feat(cli): add llmwiki rm <source> (#179)

feat(cli): add llmwiki rm <source> (#179) #488

Workflow file for this run

name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
jobs:
# Linux only — a deliberate, revisitable choice, recorded here because it is
# what let issue #163 ship: on win32 `path.sep` ("\") made every nested profile
# directory fail containment, so no profile could load, and nothing here saw it.
#
# A windows-latest leg was tried in #172 and taken back out. It confirmed the
# separator fix holds on win32, then surfaced 64 unrelated failures across 44
# files — chiefly that O_NOFOLLOW is POSIX-only, so every "fails closed on a
# symlinked leaf" guard quietly degrades to a plain open there. Nor is
# `continue-on-error` a way to land the leg non-blocking: the workflow run goes
# green but the job's check-run still reports failure and blocks the merge.
#
# So win32 behaviour is held by the `sep` test seam in `src/utils/path-confine.ts`,
# NOT by CI. Restoring this leg means fixing those 64 failures first — worth
# doing as its own change, and not free.
build-and-test:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [24]
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
cache: npm
- run: npm ci
- run: npm run release:check-docs
- run: npm run build
- run: npm test
codebase-health:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# Pin the action wrapper while using the signed 2.82.0 binary release.
- uses: fallow-rs/fallow@5cc7152083ad57f20880a14ac82262a5a6861eec
with:
version: 2.82.0
fail-on-issues: true