I’m transitioning to GIT from SVN, I’m not proficient at either, in fact, my SVN repos were just used to store code with notes and only a few revisions. That being said, I have 10-15 that I want to move to GIT for a permanent local solution.

I have followed a tutorial at: https://john.albin.net/git/convert-subversion-to-git that appeared to be just what I needed. Once I completed the procedures I had a local repo with nothing in it but the .get directory. I now understand what a “bare” init creates. I had a few errors when following the “rename ‘trunk’ branch to ‘master’”. the structure of my SVN may have been the cause of this problem as I not only have branches, trunk and tags but code files in the root of the repo.

MySVNrepo:
root:
	-code file
	-code file 
	-branches dir
	-code file 
	-trunk
	-tags
	-code file

I do have a new GIT (bare) repo with .git dir. I have no idea if my code files are present and the HEAD seems to be not as it should be. 

I have tried to clone from my bare new repo to new local directory to get a working directory… I get the error: `warning: remote HEAD refers to nonexistent ref, unable to checkout.` so via this: https://stackoverflow.com/questions/36201342/git-where-exactly-is-the-working-directory 

i try: 
1 `git ls-remote origin` that returns: `883cc296ae57326b3c2a01f3304bc7bae71bc150	refs/heads/origin/trunk` 
2 `git branch -a` returns: `remotes/origin/origin/trunk`
3 `git checkout remotes/origin/origin/trunk` returns: HEAD is now at 883cc29... initial structures
4 `git checkout -b master` returns: “Switched to a new branch 'master’”
5 `git checkout`

Still no working directory of files… I pretty sure this is all a result of my original SVN repo structure… I just need a working directory that I can commit with messages.

—————————————————————————————————————————————————————————————————————————————————————————
MORE NOTES:
list svn repo info:
svn ls http://10.0.0.200:81/repos/crowdmanager/ --verbose

git svn clone --username barclay http://10.0.0.200:81/repos/crowdmanager/ --no-metadata -A authors-transform.txt --stdlayout ~/cm-temp

MacBook-Air-13:crowdmanager jeffbarclay$ git svn clone ../crowdmanager  ../git/cm --stdlayout -A authors-transform.txt

svn mkdir REPO_URL/trunk -m "making trunk dir"

from: ~/git/crowdmanager-svn/crowdmanager
git svn clone ../crowdmanager ../git/cm --stdlayout -A authors-transform.txt

git svn clone ../crowdmanager  ../git/cm -T / -t / -b / -A authors-transform.txt

WORKING FIX (1/19/2018):

git svn clone --username barclay http://www.barclayvision.com:81/repos/crowdmanager --no-metadata --trunk=.

git svn clone --username svn http://www.barclayvision.com:81/repos/2017leavepicks -A authors-transform.txt --no-metadata --trunk=.

***

git svn clone --username barclay http://www.barclayvision.com:81/repos/crowdmanager -A authors-transform.txt --no-metadata --trunk=.

——————————————————————————————————————————————————————————————————————

********************************************* MOVE LOCAL GIT to [LOCAL BARE GIT] ******************************************

https://developer.atlassian.com/blog/2016/01/totw-copying-a-full-git-repo/

https://stackoverflow.com/questions/2199897/how-to-convert-a-normal-git-repository-to-a-bare-one

4
down vote	Simply read
Pro Git Book: 4.2 Git on the Server - Getting Git on a Server
which boild down to
$ git clone --bare my_project my_project.git
Cloning into bare repository 'my_project.git'...
done.
Then put my_project.git to the server
Which mainly is, what answer #42 tried to point out. Shurely one could reinvent the wheel ;-)	

https://stackoverflow.com/questions/12450245/getting-a-working-copy-of-a-bare-repository

up vote
18
down vote	You can simply clone the repository to another directory on the same machine:
git clone /bare/repo/dir.git
The current directory will become a non-bare clone of your repo, and you'll get a checkout of the master branch automatically. Then use the usual commands like git pull to update it as needed.
As a side benefit, this operation is very efficient — if you specify a local directory to git clone, git will try to share objects between those two repos using hard links.