Painpoint: How do you all do Version Control?

[Viktor CR]

I am finding myself struggling with file saving of historical document versions
for the lack of true Version Control or a "Save Copy" function.

Every time I do a "Save As", the new dated / versioned file name is being used as the current document name, when I actually want to continue working on the plain name document.

I've tried to find a stand-alone versioning system, that takes care of versioning outside of Affinity apps, but haven't been successful, yet. Something that works like Git, with multiple branches, but also featuring a preview, would be awesome.

[HCl]

.

[walt.farrell]

5 hours ago, Viktor CR said:

Every time I do a "Save As", the new dated / versioned file name is being used as the current document name, when I actually want to continue working on the plain name document.

I just use the older versions as my backups, and keep working in the renamed version, so I'm always working in the version with the latest name. And in thinking about it, I guess that's the way I've worked in all the other applications I've ever used, so it feels natural to me.

You can setup Git, and use its functions, and I've played with that but not enough to really give any advice. And it is still a manual effort, as after a Save you would need to go over to Git and do a Commit to get it copied out safely into the Git repository.

[Viktor CR]

12 hours ago, Return said:

You can setup an auto import folder

I'll need to try this. Their documentation doesn't mention anything like Version Control.
Thank you for bringing this feature to my attention. I'd never have known 😊