🐙

barkcli + GitHub

Sync tasks with GitHub Issues, link PRs to tasks, and auto-close issues on merge.

Setup

1

Initialize barkcli in your repo

2

Tasks are already in your GitHub repo as YAML files

3

Link tasks to issues with commit messages

4

Use barkcli sync to push tasks as GitHub Issues

Features

  • ✓Bidirectional sync with GitHub Issues
  • ✓PR linking to tasks
  • ✓Auto-close issues on merge
  • ✓GitHub Actions integration

Configuration

# .github/workflows/barkcli.yml
name: Barkcli Sync
on:
  push:
    paths:
      - ".board/**"
jobs:
  sync:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: barkcli sync --push

Frequently Asked Questions

How does barkcli integrate with GitHub?

barkcli runs a local MCP server (`barkcli mcp`) that exposes 56 tools for task and board management. You register it once in GitHub's config, and GitHub can then read tasks, claim work, link code context, and update progress.

Is GitHub integration free?

Yes. barkcli is MIT licensed and the MCP server is included in the binary — no subscription, no per-seat fee, no cloud.

Does barkcli upload my tasks to the cloud?

No. Tasks are YAML files committed to your git repository. The MCP server runs locally and never sends your board data anywhere.