Reviewable VS git-appraise

https://github.com/Reviewable/Reviewable/tree/master/careers

Reviewable is a very small, bootstrapped business that sells our code review software to some of the largest companies around. We've been around long enough to be much more stable than your average startup, yet stayed small enough to avoid crippling bureaucracy — everybody reports directly to the founder/CEO. We're engineer-centric and fully remote. However, we prefer hiring US residents and offer the usual benefits: health and dental insurance, 401(k) plans with company contributions, unlimited vacation, etc. We've built a company and a codebase where we enjoy working day-to-day and hope that you will too!

We're looking for a backend generalist with a love for problem-solving with algorithms and data structures!

Apply at https://github.com/Reviewable/Reviewable/tree/master/careers

Reviewable | Bay Area, CA, USA or Remote | Full Time | Generalist / Backend Developers | Typescript | https://reviewable.io/

https://github.com/Reviewable/Reviewable/tree/master/careers

Reviewable is a very small, bootstrapped business that sells our code review software to some of the largest companies around. We've been around long enough to be much more stable than your average startup, yet stayed small enough to avoid crippling bureaucracy — everybody reports directly to the founder/CEO. We're engineer-centric and fully remote. However, we prefer hiring US residents and offer the usual benefits: health and dental insurance, 401(k) plans with company contributions, unlimited vacation, etc. We've built a company and a codebase where we enjoy working day-to-day and hope that you will too!

Apply at https://github.com/Reviewable/Reviewable/tree/master/careers

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]: https://github.com/google/git-appraise

I believe their docs cover the scenario of reviewing someone's code by pushing your review to the git repo, and others can use `git appraise list` to see open pull requests.

https://github.com/google/git-appraise/blob/master/docs/tuto...

A trivial git-hook could be setup for automating email notifications.

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?

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 ensure changes were always pushed/pulled even without a special push/pull command for the issue tracker.

* At least one of them kept their info in the repo in a dot-prefixed directory and auto added/committed the file as changes were made; this meant a single issue could be in different statuses depending on which branch you were on and there was no overarching view.

* The rest effectively ran in parallel to the git repo, pushing and pulling their data within it but requiring their own commands to do so, so it was totally possible to clone the repo and not get the issues.

* Most of them didn't have a non-repo way to track issues, for project managers and such. One did have a webview that ran from a repo, but it was up to you to figure out how to keep it in sync with the comments/etc devs were putting in their copies of the issue tracker.

Sibling mentions git-bug, a few others:

https://github.com/aaiyer/bugseverywhere (I think this is one of the original ones)

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

https://github.com/neithernut/git-dit

https://github.com/google/git-appraise (I think this one is newest and I probably never tried it)