Kiril Videlov
Kiril Videlov
One potential way to mitigate this would be to detect this situation and persist the sqlite file somewhere other than `.git/gitbutler`. If we don't trust windows symlinks we could create...
I suspect that this is a rare scenario so for now we could have it set up as an override that is set only when/if a user experiences this issue....
Agreed that `.git/config` is likely a better place for this data - lets do that :). And also agreed that we might as well make it about the entire `gitbutler`...
Thanks for spotting this! Indeed something for us to fix
@Byron what do you think of this as a problem statement?
got it! thanks for the edits :)
I added an item at the bottom for consideration: > Consider having a "long-form" identifier that is unique in the workspace, i.e. using more characters, and using an abbreviated for...
I think a case can be made that we don't actually have good canonical identifiers that are robust. In the context of a "but status" we may want to identify...
I do agree that the IDs that we put on the JSON objects should be "full" in the sense that they are unique. I think am mainly trying to think...
Thinking about this... are we sure this is a good idea? The CLI ids were meant to be an ergonomic compromise for visual/ human consumption. The issue with adding it...