Home / Guides / Ling 3.0 Flash

Ling 3.0 Flash code review in GitHub Actions

Published July 23, 2026 · applies to pgup-ai/jbot-review-action v0

inclusionAI's Ling 3.0 Flash can review pull requests for free through OpenCode, Kilo, OpenRouter, or Command Code. OpenCode is listed in the live model catalog; the other three routes were manually verified with J-Bot Review.

OpenRouter setup in three steps

1. Create an OpenRouter API key. Save it as the repository secret OPENROUTER_API_KEY (Settings → Secrets and variables → Actions).
2. Commit the workflow. Add the file below as .github/workflows/jbot-review.yml. The :free suffix pins the zero-cost Ling route instead of leaving model selection implicit.
3. Open a pull request. J-Bot reads the base…head diff and posts diff-anchored findings with a verdict. Blocking findings are checked by a second session before they post.

name: J-Bot Code Review
on:
  pull_request: { types: [opened, reopened, ready_for_review, synchronize] }

concurrency:
  group: jbot-review-${{ github.event.pull_request.number }}
  cancel-in-progress: true

permissions:
  contents: read
  pull-requests: write
  issues: write
  checks: read

jobs:
  review:
    if: github.event.pull_request.draft == false
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with: { fetch-depth: 0 }
      - uses: pgup-ai/jbot-review-action@v0
        with:
          provider: openrouter
          model: inclusionai/ling-3.0-flash:free
          openrouter-api-key: ${{ secrets.OPENROUTER_API_KEY }}
          github-token: ${{ secrets.GITHUB_TOKEN }}

Four free routes, four exact model ids

Pick the route where you already manage credentials. Free windows, quotas, and context limits still belong to each provider.

Why Ling 3.0 Flash fits review work

• It spends compute selectively. Kilo's launch note describes a 124B-parameter mixture-of-experts model that activates about 5.1B parameters per token, aiming for useful agentic work without frontier-model latency.
• It has room for repository context. The hosted OpenRouter route exposes a 262,144-token context window, enough for the full diff plus surrounding files on many pull requests.
• It supports agent workflows. The launch description emphasizes coding, tool use, multi-turn execution, and token efficiency rather than chat-only benchmarks.
• J-Bot adds $0. The Action is MIT-licensed, with no reviewer service and no per-seat fee. During the free launch window, your remaining cost is normal GitHub Actions minutes.

Where the diff goes

• Your runner stays in control. The review session runs headless on your GitHub Actions runner with read-only repository access.
• The route determines the destination. Each provider uses its corresponding account or authenticated CLI backend. J-Bot does not proxy the diff through a hosted reviewer service.
• Fork PRs cannot read the key. GitHub does not pass repository secrets to pull_request workflows from forks.
• Blocking findings are verified. A second model session challenges each blocking finding before J-Bot posts it; nits are demoted.

FAQ

Related