#gitbug — Public Fediverse posts

𝗚𝗶𝘁𝗕𝘂𝗴:

#Git #BugTracker #GitBug

https://thewhale.cc/posts/gitbug

git-bug is a distributed bug tracker embedded in git. It uses git's internal storage so no files are added in your project.

To avoid self-hosting a full-fledged code forge, you might want to simply store issues in the git repo itself. Have you tried using git-bug, git-issue, or some other decentralized bug tracker?

* https://github.com/git-bug/git-bug
* https://github.com/dspinellis/git-issue

Last time I tried git-bug I failed to import my issues from GitHub and gave up, but maybe it works now, it seems there is a new & more active maintainer.

#GiveUpGitHub #git #BugTracking #issues #SelfHosting #GitBug

🥳🎉 "Git Bug" is here, folks! Because who doesn't dream of embedding a bug tracker right into their version control system? 🙃 Welcome to the future, where every bug is a feature, and every feature is... just another bug. 🚀🔧
https://github.com/git-bug/git-bug #GitBug #versioncontrol #bugtracker #techinnovation #softwaredevelopment #HackerNews #ngated

Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges

https://github.com/git-bug/git-bug

#HackerNews #GitBug #Distributed #OfflineFirst #BugTracker #Git #Bridges

@whynothugo Here's a more hands-on one from the #sourcehut folks: https://git-send-email.io/

After hosting my own #GitHub-style forge for many years (used #forgejo last), most of my private projects are now just plain ssh-hosted repos. Managing the ever growing complexity just stopped being worth it for me. #GitBug and #cgit (simple read-only web frontend) is all I need. Accepting patches/issues via mail only is not ideal, but not dealing with low-effort PRs and lazily filed issues is nice too.

I just migrated the 50 odd repos from my #selfhosted #Forgejo instance used for small and personal projects and deleted it (which ran #Gitea and even #Gogs before).

The dev-ops push has made it too big, slow and difficult to maintain for me (new versions frequently breaking things). 90% of the projects only need issue tracking, pull requests and a wiki anyway.

I'll now try a barebones ssh-hosted setup with git hooks, #GitBug and #markdown files instead. #minimalism

@happyborg

Do you have a link to what you've done so far? Any design documents?

#github #enshitification #p2pgit #git #p2p #gitbug #git

@toxi How’s #Codeberg handling issues, PR:s and such?

Ideally any post- #GitHub host would make use of something like #GitBug (https://github.com/MichaelMure/git-bug) or similar to have the issue data live with the code repositories

That and/or do a #Fediverse / #IndieWeb approach and have people publish their issues and pull requests on their own sites / instances and then notify the upstream repository about that. See eg: https://indieweb.org/issue

Is #Codeberg doing any of that?

git-bug synchronization via pure git commands is reasonable. So the main requirements for git-bug adaptation are now fulfilled.

#git #gitbug

https://todo.sr.ht/~splitcells-net/net.splitcells.network/122

So, I think the decision was made: I'll first do a test run with git-bug and see if it works. If this is the case, it will be my permanent solution:

https://todo.sr.ht/~splitcells-net/net.splitcells.network/122

#gitbug #opensource

#gitbug is a #Git-based #decentralized bug tracker.

git-bug is a Git extension that allows for a Git repository to have integrated, distributed bug tracking compatible with any Git host. Once a repository is initialized issues can be created through a command line, terminal, or local web interface. git-bug features bridges which can sync from and/or to various bug trackers including #GitHub and #GitLab.

Website 🔗️: https://github.com/MichaelMure/git-bug

#free #opensource #foss #fossmendations #programming