Git-appraise[1] implements that concept. From Google, no less. I've never used it, or seen it used in the wild, but it always seemed intriguing, and like the obvious approach. The web UI traction is far greater for this to have any serious usage, but I wonder if Git had that ability from the start, if the web UI concept would've taken off as it did. [1]: - Source: Hacker News / 3 months ago
I know about Google’s gerrit. I now found https://github.com/google/git-appraise, there seems to be a plethora on the issue and pr tracking side. Then the other day there was a generic/abstraction layer to write CI that abstracte over gitlab, circle ci, and GitHub actions (maybe more). I suppose all that’s left is to get some api tokens somewhere and go? - Source: Hacker News / over 1 year ago
Experimenting with distributed issue trackers in git was popular in the early 2010s, there were a whole bunch of different implementations people came up with for git. Most of them died out though, there were typically a few problems - this is what I remember offhand from experimenting with a whole bunch of them: * Some of them make a mess of some part of git; one of them put its info in separate git branches to... - Source: Hacker News / almost 3 years ago
Do you know an article comparing Git-appraise to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Git-appraise. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.