Comment by bo_Olean
10 years ago
How reasonable is it to make issue tracking and social interaction part of the SCM itself [with optional web interface] ?
git issues "This needs attention"
>> Issue #1 created
git issues
>> List of issues
git issues -u #11
>> Issue #11 up voted
>> #11 Important stuff, needs attention
git issues -d #6
>> Issue #6 down voted
git issues -f #4
>> Issue #4 flagged
Your `.git` directory would become huge pretty quickly and you would have plenty of problems with people commenting on issues without having a repo up-to-date. How would you handle conflicts in that case?
How is that a different problem than people editing code in a repo that's out of date?
You have to be a coder to participate~