I think it should now be possible to use Working Copy and Codea together without an intermediary like WCCC. Working Copy is evolving very quickly (the upcoming conflict resolving tool is very cool), and the way it handles zip imports has changed subtly. Duplicate a Codea project to test with, create a “zipped project export” and then experiment with the different zip import features Working Copy offers (unzip into folder, unzip into repository). Make changes to the Codea project (edit some tabs, change tab order, rename tabs, delete them), then repeat the process, and see whether you think it is OK as a “push” option.
Last time I tried this a few versions of Working Copy back, I think what I did was set up the repo in Working Copy first, and then created a folder in that repo called [project name].codea, then chose the “unzip to folder” option from Working Copy’s import options.
AFAIR I thought it worked OK, except when files were renamed/ deleted, and the old file would persist in the repo in Working Copy and would need to be deleted manually (not too arduous a step, just swipe the file to the right in Working Copy and hit delete). In other words, unzipping into an existing folder with files in it is like dragging a bunch of files into a folder on the desktop: it will overwrite files in the folder with the same name as those being copied, but won’t touch files whose name doesn’t correspond to any files in the new batch (ie, tabs you’ve renamed or deleted).
It could be that this behaviour has changed, so you might need to experiment. I use WCCC, so I haven’t tried this for a while.
In terms of the other direction, coming into Codea, that should be even easier with the “Export to Codea” option, the only issue being that you can only do “paste-into-project” with a new project, not an existing one, so you would lose data saved into the old project (with save project data, or assets saved in “Project:” folder etc).
I’d also be interested in hearing other people’s workflows.