I like the idea. It's something a colleague and I thought about a lot while working in QA. Essentially, issues are nothing more than versioned documents...
...except, the details. There are hundreds are minor changes made through a typical issue triage, and/or randomly through the day.
There are also log-type entries, where details get appended, rather than modified. Though this is something I wish source control supports as well -- like feature appending logs.
You'd still need a front-end and indexer to support searching and issue listings.
The fundamental idea seems sound, but there's a lot of those damn details. Though I'd not likely support the idea of the code and issues being in the same repository -- the issues have their own lifetime, and may not be code specific.
Well, that there's no saying you must put the issues in the same repository. Because it's just a file, you could track it in another repository, a cloud share, whatever works for your team.
I think you bring up a good point: comments and logs. That makes me think that this is beyond one file. We could use hashes to associate issues with individual files for comments (organized in a dedicated directory), so those won't become merge conflicts.
As I mentioned, I'll build a front-end for this - an application GUI, a CLI interface, and a VSCode plugin. That'll offer the search, browse, and modify tools.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like the idea. It's something a colleague and I thought about a lot while working in QA. Essentially, issues are nothing more than versioned documents...
...except, the details. There are hundreds are minor changes made through a typical issue triage, and/or randomly through the day.
There are also log-type entries, where details get appended, rather than modified. Though this is something I wish source control supports as well -- like feature appending logs.
You'd still need a front-end and indexer to support searching and issue listings.
The fundamental idea seems sound, but there's a lot of those damn details. Though I'd not likely support the idea of the code and issues being in the same repository -- the issues have their own lifetime, and may not be code specific.
Well, that there's no saying you must put the issues in the same repository. Because it's just a file, you could track it in another repository, a cloud share, whatever works for your team.
I think you bring up a good point: comments and logs. That makes me think that this is beyond one file. We could use hashes to associate issues with individual files for comments (organized in a dedicated directory), so those won't become merge conflicts.
As I mentioned, I'll build a front-end for this - an application GUI, a CLI interface, and a VSCode plugin. That'll offer the search, browse, and modify tools.