Skip to content
cvanfleterenPublic

About

A Lazygit clone written in java

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

781 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

jazygit

Git and your pull requests, their reviews and their CI, in one terminal UI. In the spirit of lazygit, written in Java on TamboUI.

jazygit showing the files, branches, commits and stash of a repository, with the rich diff of a changed file

jazygit showing Pr details

Highlights

  • Pull requests on the branches. Every branch shows its pull request: draft or not, its review (approved, changes requested, to review), its CI (passed, failed, running, queued), whether it is merging or in the merge queue, and how far it is ahead of and behind its base.
  • Stacked pull requests, shown as a stack (or, with S, among the other branches) and merged together with the ones below them.
  • CI checks, one by one: how long each took, or how long a running one should still take, estimated from how long it took before.
  • Rewrite history in a keystroke: reword or amend any commit, squash, fixup, drop or revert one, move commits you made on the wrong branch onto a new one, cherry-pick, and search the whole history by message, author, path or changed text.
  • A pull requests screen (Ctrl+P): this repository's open pull requests, the ones waiting for your review and your own, to read, comment on, merge or check out.
  • Worktrees: a branch, or a pull request, in a new worktree in one key. Switch between them, lock and prune them.
  • A rich diff view with line numbers and the changed words highlighted, for the working tree, commits and stashes. | shows the old and the new file side by side, { and } fewer and more lines of context. Ctrl+D shows all the diff options: git's plain diff, ignoring whitespace, and the filters that hide imports, lockfiles and the like.
  • One GitHub account per repository, without switching gh's active account.
  • Recent repositories (Ctrl+R), and outside a repository it offers to git init it or open another one.

Press ? in any pane for all its keys. There are several themes, a colour-blind friendly one among them. A repository can have a theme of its own, kept as jazygit.theme in its git configuration; set it in an includeIf "gitdir:~/work/" of your ~/.gitconfig, and every work repository has it.

The name of a new branch can start out with the same text every time, like the key of a ticket, with the cursor after it. It is kept as jazygit.newBranchNameTemplate in the git configuration:

git config jazygit.newBranchNameTemplate ART03DEV01-            # this repository
git config --global jazygit.newBranchNameTemplate ART03DEV01-   # every repository

or, for every repository in a directory, in the file an includeIf "gitdir:~/work/art03/" of your ~/.gitconfig includes:

[jazygit]
    newBranchNameTemplate = ART03DEV01-

Where a new worktree starts out is kept the same way, as jazygit.newWorktreeTemplate, and for the worktree of a pull request as jazygit.pullRequestWorktreeTemplate, which falls back to the first. A template can use {repo} (the directory of the main worktree), {branch} (with / as -), {owner} and {name} (the repository on GitHub) and, for a pull request, {number}. A leading ~ is your home directory, and a relative location is next to the main worktree. For a worktree that is not of a pull request, {owner} and {name} are known once jazygit has read the pull requests of the repository from GitHub, shortly after it starts; until then, or without gh, they are left as written, and the popup shows them so:

[jazygit]
    newWorktreeTemplate = worktrees/{repo}/{branch}          # /repos/worktrees/app/feature-login
    pullRequestWorktreeTemplate = ~/reviews/{repo}-{number}  # ~/reviews/app-42

Without one, a new worktree starts out next to the main one: /repos/app-feature-login.

Getting it

Download the jar, or the native Linux executable, from Releases. The executable comes packed; tar -xJf jazygit-*-linux-x86_64.tar.xz unpacks it as jazygit. To build it yourself, see CONTRIBUTING.md.

With Nix, the flake builds the native executable from source: nix run github:cvanfleteren/jazygit runs it, and nix profile install github:cvanfleteren/jazygit installs it. In a NixOS or home-manager flake, add github:cvanfleteren/jazygit as an input and take packages.<system>.default, or pkgs.jazygit through overlays.default. It brings its own git and gh, for when there are none on the PATH.

Requirements

  • git 2.45 or newer.
  • gh 2.48 or newer, logged in with gh auth login, for the GitHub features. Everything else works without it.
  • Java 25, unless you run the native executable.

About

A Lazygit clone written in java

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages