3 ms·
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 los
by Arbortheus 3y ago
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.
- infogulch 3y agoI 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.
- glodalitazic 3y agodo you have a link to a discussion?
- yurishimo 3y agoWe 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.
- palata 3y ago> 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.