Kanbus

Feature

Local tasks

Keep personal or exploratory issues on your own machine, out of Git, and promote them to the shared board with one command when they are ready.

Not every idea belongs on the team board. Local tasks are ordinary Kanbus issues stored in a project-local/ directory that Git ignores. You see them alongside shared issues in your own listings; your teammates never see them in diffs or pull requests. When an experiment turns into real work, promote it and it becomes a normal shared issue.

Create a local task

Add --local when you create an issue. The first time, Kanbus creates project-local/ and adds it to .gitignore, so there is nothing to set up. You can also do that step explicitly with kbs init --local.

kbs create --local "Spike: try the new auth library"

Local issues have their own event history under project-local/events/, which is ignored by Git as well.

Promote and localize

kbs promote moves an issue from project-local/ to project/, where it is tracked and shared from then on. kbs localize goes the other way, taking a shared issue off the board and into your private workspace.

# Local to shared
kbs promote kanbus-a1b2c3

# Shared to local
kbs localize kanbus-a1b2c3

The issue keeps its ID, description and comments when it moves. Localizing removes the file from project/, so commit that change for it to leave the shared board.

Choose what you see

By default, kbs list and kbs ready show shared and local issues together. Narrow the view when you need to.

kbs list                # shared and local
kbs list --no-local     # shared only
kbs list --local-only   # local only
kbs ready --no-local

The console has the same Local filter, and the metrics view counts shared and local issues separately, which helps you notice local work that is ready to promote. In Beads compatibility mode, the local filters are not supported.

Learn more