3 ms·
You could, but that would get messy quick since it would add a new commits to be merged/rebased every time somebody wants to comment. I guess the easiest soluti
by simias 6y ago
You could, but that would get messy quick since it would add a new commits to be merged/rebased every time somebody wants to comment. I guess the easiest solution would be to make it a submodule so that it could evolve at its own pace, but then you still want to be able to reference specific versions of the code in the comments, so maybe it would make more sense to make the code a submodule of the issue repo.
Maybe with good tooling that would be workable with git as it is.
- dotancohen 6y ago> You could, but that would get messy quick since it would > add a new commits to be merged/rebased every time somebody > wants to comment. How about a branch "bugtracker". A smart UI could keep this branch checked out internally. You know what, I'm going to flesh this out. If anybody has something insightful, please comment here. I'll write the first rough UI in Python CLI app, but the real value I'm looking to create is in the file formats so that other UIs can be created. I'll do issues first, then PRs, but all input is welcome. My gmail username is the same as my HN username if anybody would prefer to contact me in email.
- dotancohen 6y agoHere is the repo, PRs welcome: https://github.com/dotancohen/entomology https://github.com/dotancohen/entomology Note that this is very rough, it only has about two hours of work in it.