Of course, that's precisely the argument. Currently cloning a git repository is trivial, you can have different branches targeting different remotes etc... It's

Of course, that's precisely the argument. Currently cloning a git repository is trivial, you can have different branches targeting different remotes etc... It's decentralized at the core. An issue solution that built on top of this architecture would be very powerful and "just work" while a solution built on the side will face an uphill battle for adoption. Basically my point is that I consider issues to be an integral part of a repository's history, and it's a weakness of VCSs not to integrate it. A lot of the time I find Github comments on a feature/issue to be vastly more interesting and important than the resulting commit message.