I ran into this as my IDE is also constantly touching temporary files to maintain its state. It wasn’t copilot though, it was one drive. So I moved my work files into a local-only location, and then periodically rsync to the synced folder, excluding .git and other folders that have no business on a synced folder.
Because the workflow for a lot of people is to have projects in folders which are synced to Onedrive. That allows for collaboration with colleagues that are not using git, as well as backup/archival of files and access from different computers or online sharing. My workflow of using rsync to periodically copy the files (–exclude .git) works, but isn’t ideal. If I forget or someone else edits something, I have to manually deal with conflicts. I guess the real answer is just “not everyone is a software dev.”
I ran into this as my IDE is also constantly touching temporary files to maintain its state. It wasn’t copilot though, it was one drive. So I moved my work files into a local-only location, and then periodically rsync to the synced folder, excluding .git and other folders that have no business on a synced folder.
Why would you even have git repositories in OneDrive in the first place? Or are those local-only repos without an actual server to push to?
Because the workflow for a lot of people is to have projects in folders which are synced to Onedrive. That allows for collaboration with colleagues that are not using git, as well as backup/archival of files and access from different computers or online sharing. My workflow of using rsync to periodically copy the files (–exclude .git) works, but isn’t ideal. If I forget or someone else edits something, I have to manually deal with conflicts. I guess the real answer is just “not everyone is a software dev.”