Upstream software project

lazyworktree

Easy Git worktree management for the terminal

About lazyworktree

Easy Git worktree management for the terminal

This project links 4 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

lazyworktree repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.lazyworktree: recorded package coverageopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
lazyworktree
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

LazyWorktree is a TUI for Git worktrees. It provides a keyboard-driven workflow for creating, inspecting, and navigating worktrees within a repository. Built with BubbleTea, it focuses on fast iteration, clear state visibility, and tight Git tooling integration.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Tumbleweed

  1. Package lazyworktree

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Easy Git worktree management for the terminal

    1.49.0-1.2: x86_64

    Source: lazyworktree

  2. Source: lazyworktree

  3. Source: lazyworktree

  4. Source: lazyworktree

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.