Skip to content

Set up CI with GitHub Actions (separate fast and slow test jobs) #5

Closed

Description

@thomaspinder

Overview

Set up a GitHub Actions CI workflow that runs on push and PR to main.

Proposed Workflow

Fast Job (runs on every push/PR)

  • Matrix: Python 3.10, 3.11, 3.12, 3.13, 3.14
  • Steps:
    1. uv sync
    2. ruff check . && ruff format --check .
    3. uv run ty check
    4. uv run pytest -m "not slow" --cov
  • Target: < 2 minutes

Slow Job (runs on PR to main only, or manual trigger)

Docs Job

  • Single Python version (3.12)
  • Steps:
    1. uv sync
    2. mkdocs build --strict

Configuration Needed

  • Add @pytest.mark.slow marker to pyproject.toml if not already present
  • Ensure all MCMC tests are marked with @pytest.mark.slow
  • Add codecov upload step to fast job
  • Consider caching uv dependencies

Labels

ci, infrastructure

Activity

  1. thomaspinder commented on Jul 29, 2026

    @thomaspinder
    CollaboratorAuthor

    CI has been in place for some time: .github/workflows/main.yml runs quality (prek, uv lock --locked, ty), the test matrix over Python 3.11–3.14 with coverage and a Codecov upload, a docs build, and linkcheck, with uv caching via .github/actions/setup-python-env. The slow marker is registered (pyproject.toml:97). The one outstanding element from this issue — partitioning the MCMC suite into its own job — is tracked precisely by #45 and implemented in #159. Closing as superseded to avoid duplicate tracking; follow #45.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions