Run the Talos test suite locally:
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -e .[dev]
pytest --cov=talos --cov-report=term-missing --cov-report=xmlYou can also smoke-test the CLI against a snapshot:
cat > snapshot.json <<'JSON'
{
"wip_total": 8,
"global_max": 10,
"at_cap_projects": ["alpha"],
"backlog_total": 12,
"backlog_delta": 1,
"source": "manual"
}
JSON
talos evaluate --snapshot snapshot.json
talos status
talos explain --snapshot snapshot.jsonThe current Talos Python core has also been verified in a fresh python:3.12-slim Linux container.
The verification flow used:
docker run --rm \
-v "$PWD":/src \
-w /src \
python:3.12-slim \
bash -lc '
python -m venv .venv-linux-test
. .venv-linux-test/bin/activate
python -m pip install --upgrade pip
python -m pip install -e .[dev]
pytest --cov=talos --cov-report=term-missing --cov-report=xml
'What this verifies today:
- package install from source on Linux
- test execution on Linux
- parity for the current public Python core
What this does not verify yet:
- a Linux daemon/service wrapper
- Linux packaging or distribution artifacts
- an MLX deployment on Linux
GitHub Actions runs:
- a Python version matrix on pushes and pull requests
- coverage upload from the Python 3.12 test run
- a packaging job that builds distribution artifacts and smoke-tests the installed wheel
This repository includes codecov.yml plus a GitHub Actions upload step using codecov/codecov-action@v5.
Recommended setup for this public repository:
- Install the Codecov GitHub app for
Spitfire-Cowboy/talos. - In Codecov settings, allow tokenless uploads for public repositories or add
CODECOV_TOKENif you prefer token-based uploads. - Open a pull request and confirm that
coverage.xmlis processed.
This repository includes a root .coderabbit.yaml file so review behavior is version controlled.
To finish setup:
- Install the CodeRabbit GitHub app for
Spitfire-Cowboy/talos. - Open a pull request to let CodeRabbit read the repository config from the feature branch under review.