planhub 0.3.0

Sync local planning files to GitHub Issues.

Planhub

Planhub is a CLI app that syncs local planning artifacts (plans, issues, milestones written as .md files) to GitHub Issues via the API.

Goals

• Keep planning artifacts in git and reviewable.
• Generate/update GitHub issues and milestones from local files.
• Make planning conversational: we can edit .md files and sync later.

How It Works

Planhub keeps planning data next to the code it describes. Each repository gets a .plan/ folder containing milestones and issues as Markdown files with YAML front matter. You edit these files like normal docs, then planhub sync maps them to GitHub issues and milestones.

Installation

Global install from PyPI (recommended for CLI usage). pipx gives you a clean CLI install without polluting your system Python, and puts planhub on your PATH:

pipx install planhub

Project-local install with uv (inside your repo). This keeps the tool in a virtual environment for that repo:

uv venv
uv pip install planhub

After installing, run planhub setup once to create the global config at ~/.planhub/config.yaml (it will be created only if missing).

Commands

• planhub init
  • Creates the standard .plan/ structure in the current repo.
  • Use --dry-run to preview the folders that would be created.
• planhub setup
  • Creates the global config file at ~/.planhub/config.yaml (if missing).
  • Use --dry-run to preview what would be created.
• planhub issue <title>
  • Creates a new GitHub issue with the given title.
  • Requires credentials and a GitHub remote.origin.url.
• planhub sync
  • Reads .plan/ files and creates or updates GitHub issues and milestones.
  • Writes the GitHub number back into each file after creation.
  • GitHub is the source of truth for issue state during sync.
  • For existing issues, sync does not push local state or state_reason to GitHub; it reconciles those fields from the GitHub response.
  • Sync runs in three phases: parse files, build a sync plan, then apply it.
  • Use --dry-run to validate files without writing changes.
  • Use --import-existing to pull existing GitHub issues into .plan/. This requires credentials and a GitHub remote.origin.url.
  • Creating issues or milestones also requires credentials and a GitHub remote.origin.url.
  • Closed synced root issues are archived under .plan/archive/issues by default (or deleted when sync.closed_issues.policy: delete is configured).
  • Milestone issues remain inside their milestone folder. When milestone.md has state: "closed", sync moves the whole milestone directory to .plan/archive/milestones. If set back to state: "open", sync moves that directory back under .plan/milestones.

Credentials

Planhub can reuse your GitHub CLI session or a token stored in the environment. The simplest path is to authenticate once with gh, and the CLI will fetch a token automatically.

gh auth login

Alternatively, create a personal access token and export it:

1. GitHub → Settings → Developer settings → Personal access tokens.
2. Create a fine-grained token for the target repo(s).
3. Grant Issues: Read (and Write if you will push updates later).

export GITHUB_TOKEN=ghp_your_token_here

Suggested Data Repo Layout

.plan/
  issues/
    20260127-backlog-issue.md
  milestones/
    stage-1/
      milestone.md
      issues/
        issue-001.md
      assets/
        diagram.png

Front Matter Tips

• milestone can be a title or a number; use milestone: null to clear it.
• Use labels: [] or assignees: [] to remove them on GitHub.
• state_reason requires state: "closed".

Development

Setup

Install development dependencies:

uv sync --dev

Pre-commit Hooks

This project uses pre-commit to run code quality checks before commits. Install the hooks:

uv run pre-commit install

The hooks will automatically run on git commit. They check for:

• Code formatting and linting (ruff)
• Trailing whitespace and end-of-file fixes
• YAML, JSON, and TOML syntax
• Merge conflicts and other common issues

To run hooks manually:

uv run pre-commit run --all-files

Version Bumping

This project includes a grow.py script for bumping versions and creating releases:

./grow.py

The script will:

1. Read the current version from pyproject.toml
2. Show commits since the last tag
3. Prompt for the new version
4. Update the version in pyproject.toml
5. Create a commit with a changelog of commits since the last release
6. Create an annotated tag with the new version
7. Optionally push commits and tags to the remote repository

The changelog commit includes all commit messages since the last tag, making it easy to see what changed in each release on GitHub.

Next Steps

• Implement the parsing + GitHub sync logic.
• Add CI to validate file formats.