In Git, you can typically refer to commits by the shortest unique prefix of their SHA256 hash. So, instead of eb137af21, you can typically write:
> eb137
and IIRC git will raise an error if the prefix is ambiguous. OP, maybe you could do the same?
> eb137
and IIRC git will raise an error if the prefix is ambiguous. OP, maybe you could do the same?
I think ambiguity is not as critical as in Git here - if you look up a note code with multiple entries, it should just show you both so you can choose the right one based on context.