git-bug

Dev tools

issue tracker

SHOW HN2018

447points
94comments
#34of 2,155 in 2018
Top 2%of 2018 by points

How HN took it

MixedNo clear lean

15 positive, 19 neutral or asking, 2 mixed, 4 critical, out of 40 comments about the project. Thread score +0.31.

Idea: 10 for, 2 againstDesign: 4 for, 1 againstExecution: 0 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Bugs stored in the repo so history stays with the source code

    From 2 comments
    • I have always wanted something like this without having to move away from Git (to Fossil). A bug tracker like this allows the bug history to be tracked and remain with the source…
      foo101 on HN
    • This looks great! I'll very much consider using it for my next project, if only for the warm feeling in the stomach that my bugs are close to the project itself. Huge kudos to…
      nathell on HN
  • Elegant design that avoids a separate service

    From 1 comment
    • I love this because I started building a small utility to help me consistently track issues inside my project files like tickets/{folders}/{file }.md inside my projects, because…
      acidtrucks on HN

Objections

  • Permission model unclear for non-developer bug reporters

    From 1 comment
    • The permission model will be a problem. The population you desire to be able to update tickets is... shall we say, "larger" ? ;) than the population you desire to be able to…
      rout39574 on HN
  • Large attachments bloat the repository

    From 1 comment
    • The permission model will be a problem. The population you desire to be able to update tickets is... shall we say, "larger" ? ;) than the population you desire to be able to…
      rout39574 on HN
  • Separate push/pull commands are awkward

    From 1 comment
    • This looks great! I'll very much consider using it for my next project, if only for the warm feeling in the stomach that my bugs are close to the project itself. Huge kudos to…
      nathell on HN

Requests

  • Track which branches a bug is fixed in

    From 1 comment
    • Bugs are "retroactive" - you discover a bug, and then go on to determine the earliest point it was present. Given that, I am looking for an extremely niche but vital feature: the…
      pjc50 on HN
  • Status command showing new bugs and comments

    From 1 comment
    • I really like this. However, I'd like to know if there is something like git-bug status to see what new bugs/comments were added and git-bug reset (or checkout) to revert recent…
      yoz-y on HN
  • Integration with GitLab or GitHub

    From 1 comment
    • This is really nice. I think this would work really well as a GitLab integration i.e. Use GitLab's UI when online, but store the issues in your repository so it's available…
      Benjamin_Dobell on HN

Questions

  • How does it interact with git garbage collection

    From 1 comment
    • > git-bug store the data in separate references that are not in `refs/head`, so they are not recognized as branches How does that work with garbage collection?
      jimktrains2 on HN
  • How does it compare to Bugs Everywhere

    From 1 comment
    • Honest question: how does it compare to bugs everywhere? http://bugseverywhere.org/ has been around for a long time but services like GitHub and GitLab refuse to support its…
      eeZah7Ux on HN

Alternatives named

  • Bugs Everywhere

    From 1 comment
    • Honest question: how does it compare to bugs everywhere? http://bugseverywhere.org/ has been around for a long time but services like GitHub and GitLab refuse to support its…
      eeZah7Ux on HN
  • git-appraise

    From 1 comment
    • There is also Distributed code review system for Git repos: https://github.com/google/git-appraise
      Boulth on HN
  • SIT

    From 1 comment
    • You might be interested in SIT[1] then. SIT has an issue-tracking[2] module which is comparable to git-bug in its scope. [1]https://sit.fyi/…
      dm3 on HN
  • Artemis

    From 1 comment
    • Personally I've had great success with http://mrzv.org/software/artemis for the past few years. Issues are stored in a `.issues` directory as maildirs, so it does "leak out" into…
      chriswarbo on HN
  • git-issue

    From 1 comment
    • There's also https://github.com/dspinellis/git-issue, but I don't have any experience with it yet. Maybe it can give you some inspiration
      archseer on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/17782121)