Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,779
Community Members
 
Community Events
176
Community Groups

Bug/feature request: Please keep a backup of the config xml

A few times a year something happens to my sourcetree config files; I launch source tree and I see an error message about the settings being corrupt (I can't quite remember the message) - do I want to quit and try and fix the file or continue and reset them

 

If I take a look in some config xml (again, I forget the exact name of it) I can see that the file starts normally, and is XML like i'd expect, but at some point it just becomes full of 0x00 - it'll be right in the middle of the tag, so the structure of the XML and all the data after that point is toast

SourceTree isn't the only app I have this from; WinLESS and a couple of others, which also keep their data in XML files, do it too. I wondered if there is some failure of a microsoft XML writer librar y if the machine is hard powering down just to battery, or perhaps windows update..

Anyhow; however it happens, would it be possible for ST to just keep a  backup copy of a config when it's writing a new one, and the "reset, quit&repair yourself" options could be augmented with "use the last known good config" - it sucks to have to load 37 repos in again, and I'm not quite diligent enough to keep my own backup of the app data folder yet (but one day, when I've less on the to-do list..)

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events