... One possible solution is to change the storage format used by CODESYS SVN (which would render it incompatible to older versions of the AddOn, but might have other advantages), the other solution is to enhance the adapters so they provide a proper emulation of all needed SVN features.
Thank you Marcus, I'm sure that you are correct that it is the loss of properties that is the main issue with using the Github SVN bridge. As I only see the results of your work, and not the effort involved, I must admit I'm attracted to the idea of a format change so that only the basic SVN features are used thus allowing bridges to be used. Presumably a format upgrade process would be possible.
One further thought if you ever do look at the format used. I think it would be highly beneficial if we could re-constitute a CODESYS project from the raw files checked out of SVN using a command line script. My reason for mentioning this is for integration with continuous integration systems. I currently use jenkins, and actually check out projects twice, once using raw SVN and then using codesys (to checkout the same version).
Nice ideas for the wish list - not sure how well you can prioritise these:)