Skip to content

multi-backend-quick-reference.md

Latest commit

 

History

History
145 lines (101 loc) · 3.28 KB

multi-backend-quick-reference.md

File metadata and controls

145 lines (101 loc) · 3.28 KB
Raw

Multi-Backend Quick Reference

GitHub Issues backend is disabled by default. Set tasks.githubBackend.enabled: true in your config to enable gh# tasks. See GitHub Issues Backend Guide.

Task ID Formats

Format Example Description
Qualified mt#123 Minsky database backend, task 123
Qualified gh#456 GitHub Issues backend, issue 456

Common Commands

Task Operations

# Get task
minsky tasks get mt#123              # Minsky backend
minsky tasks get gh#456              # GitHub backend

# Create task
minsky tasks create "Task title"                    # Default: minsky backend
minsky tasks create --backend gh "GitHub issue"     # GitHub backend

# List tasks
minsky tasks list                    # Default backend only
minsky tasks list --all-backends     # All backends
minsky tasks list --backend gh       # GitHub backend

# Update task status
minsky tasks status mt#123 IN-PROGRESS
minsky tasks status gh#456 DONE

Session Operations

# Start session
minsky session start --task mt#123   # Minsky backend task
minsky session start --task gh#456   # GitHub backend issue

# List sessions
minsky session list

Cross-Backend Operations

# Search across backends
minsky tasks search "authentication" --backends mt,gh

# Migrate task between backends
minsky tasks migrate-backend --from minsky --to github --execute

Backend Configuration

tasks.githubBackend.enabled (default: false)

The GitHub Issues backend is disabled by default. Enable it explicitly:

# ~/.config/minsky/config.yaml
tasks:
  githubBackend:
    enabled: true

When disabled, --backend github or --backend github-issues throws:

GitHub-issues task backend is disabled. Set tasks.githubBackend.enabled=true in your Minsky config to use it.

Backend Prefixes

Backend Prefix Example Status
Minsky DB mt mt#123 Enabled (default)
GitHub Issues gh gh#456 Disabled by default

Troubleshooting

Common Issues

# Task not found
minsky tasks list --backend gh       # Check correct backend

# Backend not configured
minsky config validate               # Check configuration

Validation Commands

# System health
minsky config validate

# Task resolution
minsky tasks get mt#123 --debug

# Session validation
minsky session validate

Best Practices

ID Usage

# Explicit qualified IDs
minsky tasks get mt#123
minsky session start --task gh#456

Backend Selection

  • mt#: All Minsky-managed tasks (database-backed)
  • gh#: Team collaboration, public issues, external contributions

Cheat Sheet

Daily Commands

# List active work
minsky tasks list --status IN-PROGRESS --all-backends

# Quick session jump
minsky session start --task $(minsky tasks list --status IN-PROGRESS | head -1 | cut -d' ' -f1)

Status Updates

# Status update
minsky tasks status mt#123 IN-REVIEW --notes "Ready for review"

Tip: Use qualified IDs (mt#123, gh#456) for clarity in documentation and commit messages.