You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
It seems like SourceTree is constantly deleting certain avatar images. My thrash is showing that it contains items, I clear it, then after a while certain items are in the trash again. It seems to have something to do with gravatar images.
Hello everyone! This will be fixed in the next release, which should be in beta very soon. This was caused by a small change that moved deleted files in the working copy to the recycling bin, but ended up applying to all removed files.
Why does a git client ever need to move file to recycle bin instead of perm delete?
Does that mean every time I switch a branch, tons of files end up in recycle bin?
If that were the design choice SourceTree is going with, please give an option to "always permanently delete file, and never move file to recycle bin"
Thanks for reaching out!
Why do you suspect that it is Sourcetree deleting these images? Are these images part of one of your repositories? Can you give us some more context so we can understand where the issue is coming from?
Let us know,
The json files are user analytics data. Sourcetree records clicks etc then packages them into temporary json files before bulk submitting. After that it deletes the temp file.
Sourcetree pulls gravatar icons to display against accounts.
I'm guessing here but I suspect it just periodically deletes the existing one and gets it again to ensure it has the latest version. Alternatively it might be just part of the download process before the final file is written to its final location.
Finally there was a recent change in Sourcetree to support delete to recycle bin. I may well be that previously these files were explicitly deleted but now the delete to recycle bin option is on they go to the bin.
Same happens here. Even though it is a minor irritation. I still request that you fix this in a future release. It isn't the highest priority, but it was enough of an irritation that I had to Google this issue. I also knew right away that it was caused by Sourcetree because of the file locations.
I have used the software for years and (presumably) the same user analytics uploads and the same gravatar image cache was part of previous releases but they didn't end up in the recycle bin like this until v 3.2.6
When you say this can be disabled, is the option called "Keep backups on destructive operations"? That appears to be the only one that has a name similar to what you describe.
I have no problem with Sourcetree putting the deleted files in the Recycle Bin when the action was initiated by the user. In other words: if I went into my repo and deleted a bunch of files then those files can go to the bin.
This, above, is the type of behaviour of programs like VS Code. I see things in the recycle bin that I know why they are there. I can recover my own stupid actions.
However, programs like VS Code are also doing a bunch of internal actions, all day long. VS Code will add, remove, modify several files. Some are in Temp locations on my computer and others are in dedicated hidden folders like the ".vs" folder. However, none of those internal actions every end up in the recycle bin.