KingDownloads

git-bug version history

10 releases tracked, newest first.

v0.10.1

May 19, 2025
- Fixed CLI issue by ignoring missing sections when removing configuration

2 downloads

v0.10.0

May 18, 2025
To view the full set of changes, including internal developer-centric changes, run the following command: ``` git log --oneline v0.9.0..v0.10.0 ``` ### Documentation - **bridge**: correct command used to create a new bridge by @mxt-mischa in #1422 ### Features - **web**: simplify header navigation by @lygaret in #1427 - **web**: remark upgrade + gfm + syntax highlighting by @lygaret in #1444

2 downloads

v0.9.0

May 12, 2025
This release contains minor improvements and bug fixes. The full changelog can be seen by running the following command: git log --oneline v0.8.1..v0.9.0 ### <!-- 0 -->:rocket: Features - **tui**: improve readability of the help bar (23be684a05ff) ### <!-- 1 -->:honeybee: Bug Fixes - remove errata from string literal (aa102c91f675) ### <!-- 2 -->:pencil: Documentation - **dev-infra**: define stricter commit message guidelines (f680ef74a500) - correct mispelled words (89ff47a4ee5c) - clarify testing activation of the dev shell (d753637e3523) ### <!-- 4 -->:wrench: Miscellaneous - **dev-infra**: improve //:.editorconfig alignment with formatters (b4ad53215014) - **dev-infra**: add gopls to the development shell (29b59f2a3888) - use pkgs.runCommand for the pinact check drv (65f8ec981abe) - remove workflow: lifecycle (f3bb756e303e) - automatically mirror HEAD to trunk (22574726cdf5) - mark TestCache as flaky (3e5f4ee70cf9) - add support for Helper() (1ec304e638c1) - implement support for Failed() and FailedNow() (1766f85bf9ed) - add an internal lib for running flaky tests (f6e7fb524e3e) - simplify github-related variables (dac71e738c94)

2 downloads

v0.8.1

May 5, 2025
## Features - detect os.Stdin/os.Stdout mode [#994](https://github.com/git-bug/git-bug/pull/994) ([Steve Moyer](https://github.com/git-bug/git-bug/commit/146037733472eb74429d6c053ccbb8087fe70bca)) - use isatty to detect a Termios instead [#994](https://github.com/git-bug/git-bug/pull/994) ([Steve Moyer](https://github.com/git-bug/git-bug/commit/a73640150d8f5c8492140f9d81e7b84542b95763)) - add concurrency limits to all pipelines [#1189](https://github.com/git-bug/git-bug/pull/1189) ([sudoforge](https://github.com/git-bug/git-bug/commit/a4b8858668d44203f31e1d9cd675b02600d0ea3f)) - update action library versions [#1189](https://github.com/git-bug/git-bug/pull/1189) ([sudoforge](https://github.com/git-bug/git-bug/commit/eda0d6723978fa19711b538bf1e9641537959bb3)) - add initial nix development shell [#1190](https://github.com/git-bug/git-bug/pull/1190) ([sudoforge](https://github.com/git-bug/git-bug/commit/bf753031d012b106ddafff2e3bfd4422db5e4935)) - add a commit message template [#1190](https://github.com/git-bug/git-bug/pull/1190) ([sudoforge](https://github.com/git-bug/git-bug/commit/825eecefa1650737e661ad8eae4f07bb19b45ae0)) - add a common file for git-blame ignored revisions

2 downloads

v0.8.0

Nov 20, 2022
More than 800 commits and a long long time after, git-bug `v0.8.0` is now available. Once again, this release represent a push towards making git-bug generally useful and correct. The two main improvements are a new Entity framework and write-capable WebUI. ![image](https://user-images.githubusercontent.com/294669/198875994-9d1b0e70-78c2-4c18-b5c8-abcc9fc8f960.png) Introduced in this version, the code handling the data model and conflict resolution has been improved to support fully p2p sharing model, and generalized into an easily reusable framework [Documentation 1](https://github.com/MichaelMure/git-bug/blob/master/doc/model.md), [Documentation 2](https://github.com/MichaelMure/git-bug/blob/master/entity/dag/example_test.go). This is a huge step forward as it means writing new entities (configuration, pull-request, board ...) becomes nearly as simple as for a CRUD application. This entity framework makes it easy to extend git-bug, but also to use it as a library to create brand new applications using the same techniques as git-bug. Additionally, the underlying data model has been improved and fix earlier shortcoming. Notably, operations can now be represented in a

2 downloads

v0.7.2

Mar 21, 2021
This release fix a security issue where arbitrary malicious code could be executed if someone commit a `git` executable inside the repository. More details at: [security advisory](https://github.com/MichaelMure/git-bug/security/advisories/GHSA-m898-h4pm-pqfr) Users are advised to upgrade as soon as possible.

2 downloads

0.7.1

Apr 4, 2020
This is a bug squashing release. Core - cache: fix missing login in LegacyAuthorExcerpt causing panic - query langage: introduce a proper Lexer/Parser/AST to fix the brittle parsing and unlock more possibilities in the future Bridges - all: fix matching between remote and local bug potentially too lax - gitlab: fix the importer due to URL scheme change - gitlab: fix the iterator missing labels - gitlab: avoid trailing API call in the iterator - jira/gitlab: fix a bad login handling in the configurator - launchpad: fix a nil value access :bug: :rocket:

2 downloads

0.7.0

Mar 1, 2020
This release mainly feature the bidirectional Jira bridge, a dramatic webUI improvement and extensive bridges internal rework. <div align="center"> <img src="https://user-images.githubusercontent.com/294669/75617106-d52e7f80-5b5a-11ea-800d-c79c5e4a6eeb.png" /> </div> @cheshirekow faced the Jira monster and wrote a complete bidirectional bridge. At the same time, work has been done to refactor the supporting internals, generalize and strengthen it. The next bridge will be much easier to write! The webUI saw dramatic improvements with @sandhose and @ludovicm67 teaming up. Even though not everything is here yet, it already look and feel like a much more mature tool. The days of a fully featured webUI and even one open to user without git access are on the horizon. Breaking changes - bridges configuration format changed. If you had a configured bridge, you will need to remove the section in the repo git config (.git/config) and the credentials in the global git config (~/.gitconfig) and configure it again Core - metadata system for the bridge's credentials - credentials identifiers are now salted to avoid a direct relationship between the identifier and the secre

2 downloads

0.6.0

Dec 31, 2019
This release mainly feature the Github exporter, the bidirectional Gitlab bridge, extensive bridge improvements and better text support in the TermUI. <div align="center"> <img src="https://user-images.githubusercontent.com/294669/70243310-a29b0380-1772-11ea-886e-bfb2b5dafe9e.png" /> </div> Thanks to the work of @A-Hilaly during *and after* the Google Summer of Code, numerous improvements have been made on the bridges. The Github workflow is now complete, a full Gitlab bridge has been added, support for cancellation and resume make them fast and robust. An important work leading to the creation of https://github.com/MichaelMure/go-term-text has been done to provide a better text rendering in the CLI and the termUI, especially for languages with wide characters like Japanese or Chinese. Breaking changes - bridges configuration format changed. If you had a configured bridge, you will need to remove the section in the git config (in `.git/config`) and configure it again Core - Labels now have colors and are displayed in each UI and exposed in GraphQL, thanks to @ludovicm67 - text formatting for the terminal (CLI and TermUI) as been extracted into its own reu

2 downloads

0.5.0

Apr 21, 2019
This release mainly feature a huge rework of how identities are handled. While they were previously fully embedded in every single bug operations, they are now deported in their own data structure. ![image](https://user-images.githubusercontent.com/294669/56471590-80a77780-6454-11e9-8914-7b9dd13aa69a.png) Reworking `git-bug` to add this whole new identity data model has been a [long and arduous journey](https://github.com/MichaelMure/git-bug/pull/89). Indeed, the concept of identity is so central in a bug tracker that it touched pretty much every file of the project. It took two months to be able to fully compile the project again. Good thing that golang allow to proceed step by step and check that everything works with a set of tests! This work already yielded some benefits: less memory and storage usage, more performance, or simply being able to query bugs by author or participants. But the real benefit is that is will, once we add cryptographic keys to the identities, serve as a foundation to build more advanced features: - commit signature to authenticate bug edition or even code authors - an access right policy with different role (administrator , ...) - encrypted

2 downloads