Skip to content

Releases: git-bug/git-bug

0.4.0

21 Oct 10:42
2ab2412
Compare
Choose a tag to compare

This release mainly feature the Github importer, support for comment edition and an extensive UX rework for the CLI commands.

image

A new import/export framework has been added with its first offspring, the Github importer. This incremental importer will replicate into git-bug the Github issues, including the comment edition. Its complement, the exporter, is not that far away and will allow to use git-bug as an offline remote for Github.

This work on the importer really was a stress test on the data model and the code architecture. Part of that effort was to add support for comment edition. A new EditCommentOperation now allow to edit a previous comment while still keeping the data model immutable and conflict free. Due to its retroactive effect,the raw stream of operations does not anymore match what an UI should display. To remedy to that problem, the Snapshot, compiled from the stream of operations, now feature an properly processed Timeline.

Another important work, the CLI commands received a good UX cleanup to be generally more discoverable and better match the git experience. Annoyed to have to type a bug id or prefix for each command ? You can now use git bug select to have it selected implicitly for your next commands.

So, is it ready for prime time ? Not yet I'm afraid. A last needed important change to the data model is the rework of the identity management. This will likely be part of the next version, along with the Github exporter. Any help with that or any part of git-bug will be greatly appreciated. This is your time to make git-bug your tool.

Core

  • operations are now validated before being applied
  • operations can now be tagged with arbitrary key/value metadata.
  • core now support comment edition with a new EditCommentOperation

CLI

  • rename git bug new to git bug add
  • new command git bug select to select a bug for implicit use later
  • new command git bug deselect to clear the selected bug
  • git bug comment now display the comments of a bug instead of adding a new comment
  • new command git bug comment add to add a new comment
  • new command git bug title to display the title of a bug
  • new command git bug title edit to change the title of a bug
  • new command git bug status to display the status of a bug
  • open and close are now sub-commands of git bug status
  • new command git bug label to display the labels of a bug
  • new command git bug label add to add a new label to a bug
  • new command git bug label rm to remove a label from a bug
  • new command git bug ls-labels to list labels already used in the repository
  • new command git bug bridge to list configured bridge
  • new command git bug bridge configure to configure a new bridge
  • new command git bug bridge pull to

TermUI:

  • better responsible view for the bug table
  • support for opening/closing a bug, thanks to @adamslc
  • support for comment edition, thanks to @adamslc
  • better label edition, thanks to @adamslc

GraphQL:

  • the API is now auto-documented
  • the new Timeline is now exposed

And of course, the usual bug fixes and minor improvements.

🚀 ☀️

0.3.0

13 Sep 16:13
ad59f77
Compare
Choose a tag to compare

This release feature mainly the work to make git-bug both future proof and efficient.

A new caching layer has been added to serve as a backend on top of the low-level access, index bugs and keep them in memory for long lasting scenario. The index is stored on disk and allow to query a repository with 10k bugs pretty much instantly.

A query language has been implemented to be able to filter and sort the bug list.

After research, the serialization format has been changed to JSON for an easier interoperability with any other tool that may want to pickup the format. While JSON is quite verbose, it does compress very well when stored in git. The new format is also versioned to be backward compatible. Note that this is not in itself a backward compatible change, and bugs stored before will not be readable anymore. git-bug is still not considered stable for real usage, but it's fairly close now.

Thanks to @vandesign, git-bug now has a logo !

CLI:

  • git bug ls now accept either a query or flags to filter and sort the list.

TermUI:

  • you can now sort and filter the bug list with a query
  • by default, show only open bugs

WebUI:

  • labels are displayed with nice generated colors (#19)
  • GraphQL API now accept a query to filter and sort bugs

And of course, the usual bug fixes and minor improvements.

🚀 ☀️

0.2.0

17 Aug 11:46
d959acc
Compare
Choose a tag to compare

This release feature:

  • a revamped web UI
  • various fixes, especially on the terminal UI

🚀 ☀️

0.1.0

12 Aug 19:44
c1a0811
Compare
Choose a tag to compare

This first tagged version showcase the core features of git-bug, including:

  • data model to store bugs
  • push/pull to a git remote with no-conflict merge
  • a git porcelain command that serve as entry point for all the features
  • a collection of CLI commands for non-interactive usage
  • an interactive terminal UI
  • a GraphQL API for reading and editing bugs
  • a proof-of-concept rich web UI all embedded in the go binary
  • bash and Zsh completion, documentations and manpages

🚀 ☀️