Syncing/versioning issues when collaborating on same database
I am building a site with another developer. We both develop locally, are linked up to the same remote database and use git for version control.
We are having issues with LV files. Whenever the other developer edits a LV file, that change instantly syncs across to my local version of the same file. Now this is causing us versioning issues, as git thinks I edited the file (even if I haven't touched it). We've had a few scenarios now where we were accidentally overriding the other's changes and keep having to figure out who worked on what.
At the moment the only work-around we can see is to disable the 'save as file' for all variables, but that would mean having to manually copy and paste any changes we do in the CP, which is going to be a pain as we have loads of variables.
My question:
Is there any way to keep pushing changes made to the LV files to the database, but not pull them down, basically making it a one-way scenario?
Replies
Low 29 Mar 2014 12:38
Currently that's not possible without hacking the core. I'd have to look into things to see if this is a feasible feature request, as I think it might actually be trickier than it seems.