This is why I keep coming back to the idea that we need tools that keep their data serialized in the repo itself. I talking about issue tracking, project plann

This is why I keep coming back to the idea that we need tools that keep their data serialized in the repo itself. I talking about issue tracking, project planning, documentation like github wikis or confluence, all that stuff. There are quite a few problems to solve to support this that I haven't worked out properly, otherwise I'd be building it. For example, where do you keep your backlog? How do issues and issue statuses get stored? How do you report on open tickets and progress if the state is scattered across a bunch of different branches?