|
|
|
|
|
|
by nxnze
122 days ago
|
|
|
Yup, it's not the greatest solution for teams as a central issue tracker. The main reason I included the mention of small teams is that you can opt out of committing ./ghist, keeping it on your machine only and use it to track your own set of work across multiple agent sessions. It then becomes more of a disposable tool you can use to get big chunks of work done with persistent task memory. Going with sqlite might not have been the best decision either as it's ultimately a binary file that can't be diff'd. Potentially JSON might have been a better solution for this. |
|
|
Many have tried out this general idea. I myself evaluated git-bug for a few days in 2018 when it was a novel idea, but I ran into issues I tried to raise in my previous comment.
The data format you chose is not even the main issue here.
Binary data that keeps changing is generally always unfit for source control.
In your use case, you can solve that by committing sql dumps of the database in a text format.