Repository navigation
Tags
Tags
gitrl-z 0.10.0 - In the graph, the label of the checked-out branch has a pointed left end. - In the graph, the label of a local branch has the colour of its lane, as in the reflog list. The text of the label is light or dark, whichever is easier to read. The labels of remote branches, tags and the stash keep their colours. - The first lane is blue, and no lane has the colour of a remote branch or of a tag. - A lane with no activity for many rows does not stop with an arrow. It continues to the commit where the branch starts. - In the branch list, the mark of the checked-out branch comes before the name. Packages for Ubuntu 24.04 and 26.04, and an AppImage.
gitrl-z 0.9.0 - The install adds gitz, a short name for gitrlz, unless another program called gitz is on the PATH. - The reflog loop of the icon is now Olympic Blue, as in the gitrl-tools logo. - The copyright file of the package gives the correct licence for each icon file. Packages for Ubuntu 24.04 and 26.04, and an AppImage.
gitrl-z 0.8.0 A rewind now shows what it does to the files. In the Rewind to this point window, a double click on a branch that moves opens the commit it lands on, so you can check you picked the right one. The menu of the row offers that commit and, beside it, the diff of the whole move: everything between where the branch stands now and where it lands. The window opens on All branches, the reflog of every local branch with the dial above the graph. The dial keeps the moment it rests on when the repository changes below it. The stops on the dial follow the clock. The distance between two stops is the time between the two moments, so an hour of work reads as a cluster and a quiet fortnight as a gap. Long quiet stretches are drawn shorter and short bursts wider, so neither takes the whole dial nor shrinks too small to click. The menu on the branch pill of a reflog row copies the name of that branch. The rewind window takes its frame from the theme, and the right click menu shows one border instead of two. Nothing here writes to the repository.
gitrl-z 0.7.0 The whole repository rewinds. All branches in the sidebar folds the reflogs of every local branch into the moments the repository has passed through, and a dial over the graph puts every branch back where it stood at the moment it rests on, redrawing the graph at each stop. Two entries written in the same second are one moment, so a rebase that touches several refs produces a single stop. The moment can also be typed to the second. A branch that did not exist at the chosen moment is planned for removal. The reset plan expresses deletions alongside targets, and the generated command gains a branch -D line for them. The checked out branch is never offered for removal, because git cannot delete the branch it stands on. Rewind to this point opens the commands in a window of their own, above a branch by branch listing of where each branch stands and where it would go. The bar under the reflog carries only what can cost work: how many branches move, how many are removed, and how many files hold uncommitted changes. The Time and Entries limits reach the dial as well as the table. They narrow the moments on offer rather than the history those moments are computed from, so every branch position stays accurate however far the limits are drawn in. A right click in the sidebar list, or on a label in the graph, copies the name of that ref. Nothing here writes to the repository.
gitrl-z 0.6.0 The preview graph is now the history the planned command would leave. A planned branch is drawn at its target instead of its real tip, so the commits the command abandons drop out of the picture, and a stack of branches reset back to an earlier shape reads as a stack. The commit the window opened on is kept only while the plan is empty, and the caption says when it is there. A rebase that carried several branches is labelled per branch. A run with --update-refs rewrites the branch it started on and carries every branch pointing into the range; each carried branch records its own move, and those records now name the steps of the run. The command offered for a step therefore moves the branch that step belongs to. A double click on a commit in the graph opens its diff. The animation in the README is scripted and recorded again, and shows more: a reset that brings back two commits, a second branch added to the same plan, a deleted branch offered back, then a return to the present. The code comments are gone from every first-party source. Licence headers and translator notes stay, and the vendored gitg subtree is untouched.
PreviousNext