Closed ianklatzco closed 6 years ago
this is more like "i want to formally know when shit is changed and why"
You could manually write it out in a file, still... alongside explanations and use git blame
.
oh, can we track those sorts of changes? i’ve never seen eg theme settings touched by version control, so maybe they’re in the gitignore.
this is dumb and we're never gonna keep it up (i like the idea of version controlling the files than contain relevant theme configs tho and having commits be last "known good states"
makes reverting in case of minor bug easy too
can we version control and just track those two files? symlink them into a git repo in the home directory or something
what about that + a crontab entry that creates a commit like every day or something? still we would have to use context clues to figure out why changes were made, but it's better than the current affair which is basically "ddr player pokes at settings.ini
until it resembles good"
hmmm that's kinda nice
mostly i just want version control so that we have "known good" states right before tournaments and can revert directly to them. we had an issue once during a tournament.
a crontab script seems a little overengineered to solve that problem.
put this in a file or something or just upload
ThemePrefs.ini
andPreferences.ini