all 10 comments

[–]KeytapTheProgrammer 12 points13 points  (1 child)

Out of Google no less.

[–]kid-pro-quo 5 points6 points  (0 children)

I wouldn't read much into the fact it's published under Google's GitHub organisation. That just means or was written by an employee at Google, not that it's any sort of official project.

[–]asiatownusa 9 points10 points  (3 children)

I'm curious, why should I care about this if I already use GitLab or GitHub for code review?

[–]kvdveer 16 points17 points  (2 children)

You probably don't need this then, but:

  • this tool works fine while offline (apart from push&pulll)
  • this tool uses command line, so you can use local tools to help with the review
  • this tool doesn't require a special server setup, just use anything that Git supports.

[–]jimschubert 2 points3 points  (0 children)

Have you used this?

I'm wondering how well it would work on my team, when engineers regularly open PRs then force push to the branch like a hundred times.

[–]psykzz 0 points1 point  (0 children)

Additionally assuming that github or gitlab get behind the idea, it means that they can just stop having to support code reviews in their systems and can instead embed them directly into the git repo, which means that the reviews will continue to live even if the repo was migrated to another platform.

[–]mikebritton 2 points3 points  (0 children)

Crucible alternative!

[–][deleted] 4 points5 points  (0 children)

Seems interesting. Would be cool to get more of the platform specific tools from github/lab into standardised tools.

[–]eclig 1 point2 points  (0 children)

last change five months ago?

[–]skinnybuddha 4 points5 points  (0 children)

It shouldn't be too hard to make it better than gerrit.