|
|
|
|
|
by jeremyjh
10 days ago
|
|
The more important thing about issues & PRs is that they explain why the code is the way that it is. Knowing why the code is the way it is, is almost the entire reason we have a repository to begin with. They belong to the code, not some social graph. Yes, code is largely about communication as well - with others as well as our future selves. That doesn’t mean it’s a social media experience. There are lots of ways to communicate that aren’t that. |
|
https://github.com/google/git-appraise
The idea is to use git-notes for issues & PRs, because git is already distributed by design and these elements of SDLC centralized our usage.