Navigate a directory full of directories, identifying repos and worktrees
add fuzzel --multi pipeline example ticket
+1
+1
.beads/issues.jsonl
+1
.beads/issues.jsonl
···
17
17
{"id":"is-tree-all-default-output","title":"--all should affect default output format","notes":"Currently --all processes all subdirectories but the default output remains minimal (status + directory). When scanning many repos, the default should likely include more useful columns like ahead/commit-date.","status":"open","priority":2,"issue_type":"task","owner":"rektide+git@voodoowarez.com","created_at":"2026-03-15T22:43:14Z","created_by":"rektide de la faye","updated_at":"2026-03-15T22:43:14Z","dependency_count":0,"dependent_count":0,"comment_count":0}
18
18
{"id":"is-tree-uh7","title":"Implement basic Git and Jujutsu detection","description":"Implemented basic detection logic in src/detect.rs using .jj and .git metadata. Jujutsu worktrees detected by checking if .jj/repo is a file (pointer) vs directory (main). Git worktrees detected by checking if .git is a file (pointer) vs directory (main). Priority: Jujutsu takes precedence over Git. Verified against example directories: compfuzor (git), compfuzor-x (worktree-git), niri-mcp (jj), niri-mcp-x (worktree-jj).","status":"closed","priority":2,"issue_type":"task","assignee":"opencode","created_at":"2026-01-09T01:41:12Z","created_by":"rektide","updated_at":"2026-01-09T03:35:17Z","closed_at":"2026-01-09T03:35:17Z","close_reason":"Completed","dependencies":[{"issue_id":"is-tree-uh7","depends_on_id":"is-tree-xxv","type":"parent-child","created_at":"2026-01-09T01:41:48Z","created_by":"rektide de la faye","metadata":"{}"}],"comments":[{"id":"dcfc6637-7594-457d-8e2f-bc268e1e0b2f","issue_id":"is-tree-uh7","author":"rektide","text":"Reopened","created_at":"2026-01-09T03:35:12Z"}],"dependency_count":0,"dependent_count":0,"comment_count":1}
19
19
{"id":"is-tree-xxv","title":"Command Options Epic","description":"Implement all CLI command options for is-tree including sorting, filtering, formatting, and output options.","status":"closed","priority":2,"issue_type":"epic","created_at":"2026-01-09T01:40:57Z","created_by":"rektide","updated_at":"2026-01-09T10:20:39Z","closed_at":"2026-01-09T10:20:39Z","close_reason":"Completed","dependency_count":0,"dependent_count":0,"comment_count":0}
20
+
{"id":"is-tree-fuzzel-pipeline","title":"document fuzzel --multi pipeline example for tree selection","description":"## Overview\n\nDocument an example pipeline using [fuzzel](https://codeberg.org/dnkl/fuzzel) (Wayland launcher) in `--multi` mode as an external interactive picker for is-tree output. This gives users a GUI-driven tree selection workflow without needing a built-in TUI.\n\n## What it does\n\n- Add an example in README or doc/ showing:\n ```\n is-tree --all --format \"{directory}\" | fuzzel --dmenu --multi\n ```\n- Show how to pipe selections into actions:\n ```\n is-tree --all --format \"{directory}\" | fuzzel --dmenu --multi | xargs -I{} reforrest push {}\n ```\n- Document useful flags: `--dmenu` for stdin mode, `--multi` for multi-select, `--prompt` for labeling.\n- Show integration with `--filter` to pre-scope (e.g. only jj trees, only stale trees).\n\n## Key considerations\n\n- Fuzzel is Wayland-native; could also mention rofi/wofi equivalents for X11 users.\n- This is a documentation/example ticket, no code changes required.\n- Complements the built-in interactive picker (is-tree-interactive-picker) as a lighter-weight alternative.","status":"open","priority":3,"issue_type":"task","owner":"rektide+git@voodoowarez.com","created_at":"2026-04-06T21:34:32Z","created_by":"rektide de la faye","updated_at":"2026-04-06T21:34:32Z","labels":["docs","example","fuzzel","pipeline"],"dependency_count":0,"dependent_count":0,"comment_count":0}
20
21
{"id":"is-tree-vite-plus-toolchain","title":"evaluate and adopt vite-plus toolchain from ~/src/vite-plus","description":"## Overview\n\nAdopt the vite-plus (`vp`) toolchain from the `~/src/vite-plus` project for is-tree's JS/TS-adjacent tooling needs (formatting via `oxfmt`, linting via `oxlint`, etc.). This is relevant if reforrest or is-tree grows any JS tooling, config files, or if we want consistent formatting across the project ecosystem.\n\n## What it does\n\n- Survey `~/src/vite-plus` to understand the `vp` CLI, its capabilities (fmt, lint), and configuration.\n- Determine what makes sense to adopt for this project (is-tree/reforrest are Rust, but may have adjacent JS needs).\n- Document or configure accordingly.\n\n## Key considerations\n\n- is-tree is primarily Rust — only adopt if there's a concrete JS/TS surface area.\n- May become more relevant if reforrest grows plugin/scripting support.","status":"open","priority":3,"issue_type":"task","owner":"rektide+git@voodoowarez.com","created_at":"2026-04-06T21:21:39Z","created_by":"rektide de la faye","updated_at":"2026-04-06T21:21:39Z","labels":["toolchain","vite-plus"],"dependency_count":0,"dependent_count":0,"comment_count":0}
21
22
{"id":"is-tree-reforrest-watchman","title":"reforrest watchman: daemonized proactive sync","description":"## Overview\n\nAfter the core `reforrest` CLI push tool is built, extend it with a long-running daemon mode that uses filesystem watching (inotify/FSEvents) to proactively detect changes in local git/jj trees and automatically sync them to remotes in near-real-time.\n\n## What it does\n\n- Watches configured source directories (e.g. `~/src`) for filesystem events.\n- Detects when new commits are created in any git/jj tree.\n- Automatically triggers push operations for trees with new local state.\n- Debounces rapid changes (e.g. during a rebase or interactive session) to avoid thrashing.\n- Maintains a small state file to track last-synced refs per tree.\n\n## Key considerations\n\n- Must not interfere with ongoing operations (debounce window, lock detection).\n- Should gracefully handle trees being added/removed while running.\n- Configurable sync interval / debounce window.\n- Logging of sync activity for debugging.\n- Signal handling for clean shutdown.\n\n## Dependencies\n\n- Requires the core `reforrest` CLI (is-tree-reforrest-cli) to be implemented first — this ticket reuses its discovery and push logic.","status":"open","priority":3,"issue_type":"feature","owner":"rektide+git@voodoowarez.com","created_at":"2026-04-06T21:11:45Z","created_by":"rektide de la faye","updated_at":"2026-04-06T21:11:45Z","labels":["daemon","replication","watchman"],"dependency_count":0,"dependent_count":0,"comment_count":0}
22
23
{"id":"is-tree-3ub","title":"Add expanded --help with detailed parameter info","description":"Implemented expanded --help with detailed information about sort, filter, and format parameters. Used clap's after_long_help to add comprehensive documentation only when --help is used. The -h help remains condensed while --help shows detailed parameter documentation including examples for filter types, sort columns, and format columns.","status":"closed","priority":3,"issue_type":"task","assignee":"opencode","created_at":"2026-01-09T10:38:06Z","created_by":"rektide","updated_at":"2026-01-09T10:40:02Z","closed_at":"2026-01-09T10:40:02Z","close_reason":"Completed","dependency_count":0,"dependent_count":0,"comment_count":0}