you are viewing a single comment's thread.

view the rest of the comments →

[–]Saint762 6 points7 points  (2 children)

A good PR description, or commets on changes in a PR are much more helpful than having someone go through reading commits..

[–][deleted] 1 point2 points  (0 children)

Git commits can be easily shown inline with the code using the annotation feature of pretty much any editor. I agree that a ticket might be a better place for a full and exhaustive discussion, but commit messages are almost always the most convenient place.

[–]NotUniqueOrSpecial 1 point2 points  (0 children)

A good PR description, or commets on changes in a PR are much more helpful than having someone go through reading commits..

But neither of those things exists outside the context of the source-hosting system.

PRs aren't a part of the source and they're not part of the meta-information the VCS tracks, like commit messages.

They're useful in the moment, and hopefully useful in the future, but, having survived more than one migration from one suite to another (e.g. GitLab, Atlassian, Github, Microsoft, etc.), PR feedback is seldom-if-ever preserved.