101–110 of 110 posts
I personally hate how all these platforms like GitHub, GitLab, BitBucket, etc slapped a centralized relational database to manage issues, comments, merge requests, etc next to a distributed de-centralized system like Git. I especially hate how they've integrated CI/CD into the Git platforms. I loathe the fact that Microsoft has tied their AI to their Git platform. I want my CI/CD to be agnostic. I want my AI to be ag…
I use this to note potential issues in my copy of the Git project. For outright bugs though I report them to the project.
awesome to see a user in the wild! if you weren't aware, you can publish your git-bug issues to the project's issue tracker, assuming that it's on one of the supported bridges today (github, gitlab, jira). the bridges exist within git-bug to support adoption of the tool and interop with existing platforms. `git bug bridge pull` and `git bug bridge push` use the bridge's API, and don't attempt to pull from or push to…
Earlier quoted context omitted.
maintainer here - this is great feedback! i recently rewrote the README because i felt like its previous iteration was a bit _too_ dense. i may have gone a bit overboard on moving things :) FWIW, the screenshots you're looking for currently live in: https://github.com/git-bug/git-bug/blob/bd936650ccf44ca33cf9...
This would be amazing as a Magit module for Emacs. I don’t relish the idea of using it in a terminal alongside Emacs while using Git from inside Emacs. Is there a lower-level interface that Magit could provide a porcelain for, maybe?
is a "magit module" roughly synonymous with a vim plugin? if so, then would shelling out to the CLI work?
Earlier quoted context omitted.
awesome to see a user in the wild! if you weren't aware, you can publish your git-bug issues to the project's issue tracker, assuming that it's on one of the supported bridges today (github, gitlab, jira). the bridges exist within git-bug to support adoption of the tool and interop with existing platforms. `git bug bridge pull` and `git bug bridge push` use the bridge's API, and don't attempt to pull from or push to…
Thanks. I can’t push it to the issue tracker since they don’t have one. Bug reports go to the mailing list.
Earlier quoted context omitted.
All those users are why bug trackers are annoying. I don't care about those fields "those other people" are demanding, why do I need to fill them out. Mean while they don't care about the fields that are critical for me and don't want to fill them out.
There's no I in team... Or to put it another way, those other 'useless' fields that take minutes may save the company hours of time in places that you don't see.
But there's U and I in unity!
/s aside, you have a valid point there: just because "I" find the field useless, it doesn't mean that it isn't out to actual good use downstream.
Earlier quoted context omitted.
This would be amazing as a Magit module for Emacs. I don’t relish the idea of using it in a terminal alongside Emacs while using Git from inside Emacs. Is there a lower-level interface that Magit could provide a porcelain for, maybe?
i have no understanding, beyond that of a lexical nature, what a "magit module" is. i'm a (neo)vim user, and heavy terminal junkie, and if i wanted to build a vim plugin for git-bug, that plugin would likely be shelling out to the command line (as git-bug doesn't expose an independent API today -- it's only started when you start the web ui). is a "magit module" roughly synonymous with a vim plugin? if so, then would…
Earlier quoted context omitted.
+1 for this. I love having a self-contained, syncable GitHub-lite. It uses SQLite for the format, too, which makes it easy to discover the internals. It just needs some more 'modern' themes
> It uses SQLite for the format My chance at sharing Fossil is not Relational . The two times it's been submitted to HN it didn't gain votes. https://fossil-scm.org/home/doc/trunk/www/fossil-is-not-rela...
Plus, the only thing I need to do to transfer it to a new disk or network location is to move the `.fossil` file, since everything is nicely self-contained.
Earlier quoted context omitted.
Thanks. I can’t push it to the issue tracker since they don’t have one. Bug reports go to the mailing list.
hrm... what's your current workflow like? if there's anything you think git-bug could be doing to make that workflow easier, would you mind hopping in our matrix channel [1], or opening an issue [2]? [1]: https://matrix.to/#/#git-bug:matrix.org [2]: https://github.com/git-bug/git-bug/issues
All I would like as a nice-to-have is support for making those issue keys that I use automatic. For me it’s all local to me so it doesn’t need to be globally unique. But those N-letter prefix does make collision less likely on a single project. I’ve mentioned it here: https://github.com/git-bug/git-bug/issues/75#issuecomment-19...
Earlier quoted context omitted.
All those users are why bug trackers are annoying. I don't care about those fields "those other people" are demanding, why do I need to fill them out. Mean while they don't care about the fields that are critical for me and don't want to fill them out.
There's no I in team... Or to put it another way, those other 'useless' fields that take minutes may save the company hours of time in places that you don't see.
Earlier quoted context omitted.
All those users are why bug trackers are annoying. I don't care about those fields "those other people" are demanding, why do I need to fill them out. Mean while they don't care about the fields that are critical for me and don't want to fill them out.
Every job has a part people don't like that's necessary. The company you work for pays you money to fill the fields out, you fill them out, you get paid.