git-appraise – Distributed Code Review for Git

1. git-appraise

   1 11 5,141 2.3 Go

   Distributed code review system for Git repos

   

   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.

2. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

3. git-appraise-web

   2 2 218 0.0 HTML

   Web UI for git-appraise

   

   I tried https://github.com/google/git-appraise-web, with a review made only locally, not pushed to the remote, but it doesn't seem to work. Did I miss something? I went up to accepting the request, so the command line is working, but the web GUI - at each step - only shows a closed request [0], and clicking on it gives an empty page.

   [0] https://ibb.co/HTg8Jfc

4. prr

   3 1 313 6.4 Rust

   Mailing list style code reviews for github

   

5. git-from-the-bottom-up

   4 32 851 0.0

   An introduction to the architecture and design of the Git content manager

   

   Very tangential:

   Gerrit also stores some of its configs in a git repo. I was setting up a new instance, but couldn't get Admin permissions because the way my auth front-end didn't play well with the docker image's assumptions.

   Gerrit already does a lot of its work via non-standard references. For example, you don't push to a branch, `refs/branches/foo`, you push to a separate `refs/for/foo` namespace that creates the review.

   Similarly, Group config is stored in the All-Users git repo [1], but in references created after a UUID, in `refs/groups/UU/UUID`.

   I ended up having a to exercise the plumbiest of plumbing commands [2] to create a new commit from scratch (from a tree, from the index, from blobs), to update the group ref to add myself to the Administrators group (this, of course, requires a local shell and permissions on the Gerrit host). It was a great way to exercise what I had learned in Git from the Bottom Up [3]

   [1] https://gerrit-review.googlesource.com/Documentation/config-...

   [2] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects

   [3] https://jwiegley.github.io/git-from-the-bottom-up/

6. awesome-git-addons

   5 1 2,016 3.3

   :sunglasses: A curated list of add-ons that extend/enhance the git CLI.

   

   please make a pull request to add this to awesome git lists, like https://github.com/stevemao/awesome-git-addons for example! this is so cool

7. git-appraise-eclipse

   6 1 34 10.0 Java

   Discontinued Distributed code review for Eclipse

   

8. git-issues

   7 1 256 10.0 Python

   A distributed issue tracking system based on Git repositories, written in Python

   

   There was an attempt at some point to build decentralized issue tracking into git: https://github.com/duplys/git-issues

   I was always a bit disappointed that it didn't catch on, but I realize it would require a UI and probably buy-in from companies like Github and Gitlab, whose whole business is based around the lack of these features in git, so it was DoA, unfortunately.

9. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

10. git-bug

    8 60 8,254 7.9 Go

    Distributed, offline-first bug tracker embedded in git, with bridges

    

    As a sort of spiritual successor to git-appraise, I've been working on git-bug[1] which support issues and will at some point support kanban and code review. There is a few notables improvements:

    - CRDT-like reusable data structure [2][3] for true p2p workflow and easily create new entities (code review ...)

    - bidirectional bridges to github, gitlab ... to ease the transition or just use git-bug as a complement of those platform

    - CLI, terminal UI and web UI, for different taste and integrate into your tooling/workflow

    [1]: https://github.com/MichaelMure/git-bug

    [2]: https://github.com/MichaelMure/git-bug/blob/master/doc/model...

    [3]: https://github.com/MichaelMure/git-bug/blob/master/entity/da...

11. asv

    9 3 898 9.0 Python

    Airspeed Velocity: A simple Python benchmarking tool with web-based reporting

    

    > All these workflows are a derivation of the source in the repository and keeping them close together has a great aesthetic.

    I agree. Version control is a great enabler, so using it to track "sources" other than just code can be useful. A couple of tools I like to use:

    - Artemis, for tracking issues http://www.chriswarbo.net/blog/2017-06-14-artemis.html

    - ASV, for tracking benchmark results https://github.com/airspeed-velocity/asv (I use this for non-Python projects via my asv-nix plugin http://www.chriswarbo.net/projects/nixos/asv_benchmarking.ht... )

12. forgefed

    10 24 999 5.7 Bikeshed

    ForgeFed - Federation Protocol for Forge Services

    

13. local-code-review

    11 1 3 5.5 Shell

    Scripts to enable viewing a pull request as a local pending merge

    

    Here's a script I use for this. It's designed for use with github. Run it in your copy of a repo with a PR number and it will create a 'review' branch that has the changes uncommitted. Works great with IDEs with a good diff experience.

    https://github.com/whenceforth/local-code-review

Suggest a related project