git-appraise – Distributed Code Review for Git

Re:git-appraise – Distributed Code Review for Git by Arbortheus on Friday August 11, 2023 @02:20AM (#37085676)

I assume it would also have the advantage of not tying the code reviews and PRs to a proprietary git provider.

Say I move from GitHub to GitLab, I assume I lose all the PR descriptions and comments people have made over the years and only keep the commit messages.

It would be nice to have a provider-agnostic representation of this data.

[ Parent | on HN ]

Re:git-appraise – Distributed Code Review for Git by infogulch on Friday August 11, 2023 @03:08AM (#37085940)

I seem to recall the gitea project working on something like git-tracked metadata (PRs, issues, etc), at least the idea has been floating around for a while. One problem with this idea that I haven't seen a good solution for is serializing issue numbers across distributed forks. Maybe we would give up nice sequential numbers and settle for hashed issue refs.

[ Parent | on HN ]

Re:git-appraise – Distributed Code Review for Git by glodalitazic on Friday August 11, 2023 @03:18AM (#37086002)

do you have a link to a discussion?

[ Parent | on HN ]

Re:git-appraise – Distributed Code Review for Git by yurishimo on Friday August 11, 2023 @04:53AM (#37086534)

We could also hash the issue with a time sensitive UUID. Then they could be ordered but unique to each person assuming they don't create an issue in the same microsecond.

[ Parent | on HN ]

Re:git-appraise – Distributed Code Review for Git by palata on Friday August 11, 2023 @04:39AM (#37086436)

> It would be nice to have a provider-agnostic representation of this data.

Isn't the (original) e-mail workflow exactly that? Git was designed for it.

[ Parent | on HN ]