When running gin upload <filename> not only changes to the target file will be committed, but any lock/unlock changes to files in the repository will be committed. This can lead to unintentional changes of committed files states. I would expect gin upload <filename> to only consider changes to the specified file.
This issue refers to the GIN command line client 1.11 Build 001459 (103e923620de08ff77cf290e0b840a6d66cebfe1)
When running
gin upload <filename>
not only changes to the target file will be committed, but any lock/unlock changes to files in the repository will be committed. This can lead to unintentional changes of committed files states. I would expectgin upload <filename>
to only consider changes to the specified file.This issue refers to the GIN command line client 1.11 Build 001459 (103e923620de08ff77cf290e0b840a6d66cebfe1)