Exchanging source control from Git to SVN in Xcode

Question

My project previously was in the Git source control (cloudforge.com). Now I want to exchange it to SVN source control. (Why not, my team members are not familiar/feel-comfort in Git). But when I want to checkout it already shows that it is yet in the Git source control.

I can't delete my project from git. It shows this error

But I have configured this project into svn by other Mac mini and able to checkout and commit.

My Question:

1. Why I can't checkout this project from this Mac as I can do it from other Mac?

OR

2. How can I delete my project from the first screenshot? Because there I can't find any option to delete.

Answer 1

Are you wanting to import your complete git repository into a Subversion repository, including history and log information? Or are you simply wanting to take a snapshot of your current project and make a Subversion repo out of it?

If you want to import the full history, then this may or may not be possible. Git supports branching/merging schemes that Subversion can't handle. It's only possible for fairly simple, linear project histories. See this other question for more details and options.

If you only want to move your current code snapshot into a different repository type, then the process should be relatively straightforward. All of git's metadata is stored in a normally-hidden folder in the root of your working copy named .git. Most IDE's flag a project as being connected to a git repository based on whether this folder is present and whether it has the expected contents. I'm not 100% certain about xcode, but here's what I typically do with other IDEs:

1. Make a copy of the working copy directory
2. Delete the hidden .git directory from the copy (plus any metadata files created by your IDE)
3. Import the copy into the IDE as a new project

At this point, your working copy will have no metadata and the IDE shouldn't associate it with any particular repository or version control system. You should now be able to import it into a Subversion repository using the same process that you would for a new project.