What does

lakectl local

consider to be a "change"? It appears that running

touch

on a file tracked by it, so that only the modification time changes, is sufficient to have it show up in

lakectl local status

as a change, and then get re-pushed in it's entirety when

lakectl local commit

is run. Is there a way to avoid this so that only changes to file contents cause a diff in a commit?

Hi @Aaron Taylor Please refer to https://github.com/treeverse/lakeFS/issues/8113. Please feel free to comment there

Thanks, I left a comment! I see it's a recent issue, but any insights you can share into where it and

lakectl local

improvements generally fit in the current lakefs roadmap?

It is indeed a recent issue raised last week on the same subject. As it seems like an issue that affects many users, it will probably be prioritized in the coming weeks.

Great to hear, thank you!