← Back to context

Comment by nextaccountic

3 hours ago

For me the main issue with git-bug is that they are not dogfooding it. However, it's also one of the few projects that is actually trying to solve the core problem, rather than skirting around it. (well I now learned of radicle in this thread and they seem to store issues in git and even have PR support I think)

> For me the main issue with git-bug is that they are not dogfooding it.

This is incorrect.

    $ git remote get-url origin
    ssh://git@github.com/git-bug/git-bug.git

    $ for n in bugs identities; do echo "${n} on the remote: " $(git ls-remote origin "refs/${n}/\*" | wc -l); done
    bugs on the remote:  453
    identities on the remote:  311

See the related issue for more info: https://github.com/git-bug/git-bug/issues/1221#issuecomment-...

That said, yes, GitHub is still our source of truth, as our web application does not currently support "guest" access, and there are other platform features that our community uses that we do not currently have support for (e.g. discussions and pull requests). Big changes to the web ui are coming soon, which will help to unlock the ability to do these things.

I've also been in talks with the Radicle team about possible collaboration.

  • Glad to hear about the web UI changes, git-bug has been really great for my projects that exist across forges so I look forward to testing it out :)