Search Results for "ui"

...It is fast, listing bugs or opening them is a matter of milliseconds. git-bug doesn't pollute your project, no files are added in your project. git-bug integrates with your tooling, use the UI you like (CLI, terminal, web) or integrate with your existing tools through the CLI or the GraphQL API. git-bug bridges to other bug trackers. Use bridges to import and export to other trackers. An interactive terminal UI is available using the command git bug termui to browse and edit bugs.

You've heard it before, git is powerful, but what good is that power when everything is so damn hard to do? Interactive rebasing requires you to edit a goddamn TODO file in your editor? Are you kidding me? To stage part of a file you need to use a command-line program to step through each hunk and if a hunk can't be split down any further but contains code you don't want to stage, you have to edit an arcane patch file by hand? Are you KIDDING me?! Sometimes you get asked to stash your...

...A query language can be used to filter refs and commits, see the Documentation section for more information. Commits and refs can be filtered using a query language. Changes to the repository are captured by monitoring the filesystem allowing the UI to be updated automatically. Organized as tabs and splits. Custom tabs and splits can be created using any combination of views. Vi like keybindings by default, key bindings can be customized. Custom themes can be created. Mouse support. Commit Graph.grv is currently an alias used by oh-my-zsh. Add unalias grv to the end of your .zshrc to invoke GRV.