1 CircleCI for developers
mooki edited this page 2026-11-14 16:18:54 +00:00

CircleCI for developers

Proposed, not merged: Longshot PR 417, LongshotLauncher PR 65 and Site PR 10. Reviews are open. These steps prepare access and describe the proposal, not the CI currently guaranteed by main.

Developer setup

  1. Create a CircleCI account. Share your CircleCI username in the team's CircleCI discussion so a maintainer can add it to the MagicBeanDev organisation.

  2. Install the CLI using CircleCI's official guide, then authenticate yourself:

    circleci auth login
    
  3. In a checkout containing the proposed setup, use its pinned tools and install the hooks once:

    mise install
    mise run setup
    

    Each repository has its own mise.toml, pre-commit configuration and optional devcontainer. These are proposal files, not an instruction to expect them on main.

  4. Before pushing, run the local CI checks:

    mise run lint
    mise run test
    

    Read your repository's CI guide for prerequisites and additional validation. These commands are not a claim that every remote job ran locally.

  5. To connect Claude Code to CircleCI:

    claude mcp add --transport http circleci-mcp-server https://mcp.circleci.com/v1/mcp
    

    Open /mcp, then Authenticate. Cursor users can search for CircleCI in its MCP marketplace. The server can read failures and rerun jobs; grant rerun authority deliberately.

  6. For documentation lookup without a CircleCI account:

    claude mcp add --transport http circleci-docs https://circleci.mcp.kapa.ai/
    

Intended flow and current limits

The announced plan is affected-file checks on PRs, full checks on main, and a nightly only after those checks pass. Longshot and launcher v* tags build, sign and publish. Pipelines report ci/circleci: gate. Fork PRs need a maintainer's ci: approved label. Website-changing PRs get a preview link.

This remains under review: the inspected Longshot draft has a separate nightly-release workflow, so the announced all-checks-before-publication guarantee is not established. Site has no tag-release job. Existing Forgejo workflows remain during the proposed transition.

Canonical proposal guides