You've created a repository! That's not what you have to do on your local machine[1].
You work on your workingcopy (svn lingo), not on the repository.
The repository is the storage where svn stores all the revision-data and meta-data (like commit comments, dates, etc. pp.)
So to create a playground you could try these steps:
1. Create a repository somewhere else (on your NAS, or for example in C:\repos\); just create a folder there and name it mars2020repo. The name is not important, I just chose that one to make it easier to see that this is the repository!
So, right-click on the folder and select "Create repository here";
Then select "Create folder structure"[2]
This repository is usually somewhere else (like on github for example)
2. Now we set up your working-copy
Go to a directory (or create one) where you like to work on (hence the name workingcopy). In our example C:\Orbiter\Mars2020\
There you right-click and select "SVN checkout...". This is where you "connect" or "link" your workingcopy to the repository.
In the field "URL of repository" you enter the ...guess what... the URL of the repository
In our example: file:///C:/repos/mars2020repo (You can click the three dots to browse to the folder)
Once the URL is set, clicking on the three dots again now will open up the Repository Browser Dialog, where you should select the'trunk' folder which will alter the
"URL of repository" to "file:///C:/repos/mars2020repo"[3]
Now click O.K and your working copy is set up!
3. As we've just created an empty repository nothing else will happen, just a (hidden) .svn folder is added to your workingcopy.
4. Now if you want to add files under version-control you have to tell SVN so.
So in our playground you can just add (copy) any files / folders there, but nothing special will be done with then.
SVN treats all your files as 'local' unless you tell it to "version" it.
So let's do that: Let's assume you've copied one file in there (test.txt). Now yo can either right-click on just the file or on its parent directory (in this case your workingcopy) and select "Add...". Depending on whether you've clicked on the file or on the directory the file will be just added or a selection dialog will pop up.
5. Now you have to understand that this changes are currently only known to your workingcopy (the repository did receive no change at all)
When you are ready to commit your changes right-click again on the parent directory and select "SVN Commit...".
This presents you with an overview of your current local changes (one added file that is).
You should now enter a meaningful comment (like "Added very important 1st file") and hit OK.
NOW the changes are saved to the repository! You can do whatever you like with your workingcopy, that revision (svn lingo) is there to stay!
6. Now making changes to the file is a similar approach:
Just change the content of the file and whenever you feel like it's worth to commit right-click again on the parent directory and select "SVN Commit...".
Again an overview of your current local changes will be presented (one changed file). You can double-click on that file in that list to get a nice comparison (diff) of the before and after.
Again, enter a meaningful comment (like "Did changes to make the file change") and hit OK.
Again we have created another revision in the repository...
7. Now play around a bit!
Important to note is, thar renaming a file or moving a file that is under version-control has to be done via the according right-click SVN operations!
Else it would look for SVN as if you have just deleted the file and created a new one....
But all that details are something you have to learn...
8. In our example you are the one and only developer that is commiting to that repository, but imagine another developer also changing (and commiting) things:
In this case you have to "Update" (svn lingo) your workingcopy from time to time to get those changes. Usually you do this before you start making any changes, as conflicts might arise when you have change for example the same line than the other...
If you have started working on r.2 (revision 2 - svn lingo) while the other developer already has committed three more changes,
you will get a warning (or error?) when you try to commit, that you 1st have to update your workingcopy (to r.5 in this example).
If you like to checkout the Mars2020 repository from github into any local workingcopy, the URL is:
https://github.com/schnepe2/Marsrover2020.git/trunk
You can mess around there, too
...[4]
The only difference is, that the repository is at github. So expect a login/password dialog sometimes
git is another beast, so don't ask me about details there...
I hope I didn't overwhelm you too much (or even worse: you already know all this stuff
)
And if this seems TO MUCH HASSLE for now,
a) don't be afraid, you'll get used to it and the even LIKE it.
b) you can of course always keep your habit of developing locally by copying/renmaing/moving/ZIPping files. It's just not collaborative
/Kuddel
[1] you can of course do so. And it's a nice way to play around with svn! But you have to remember to know the difference between workingcopy and repository
[2] This creates sub-folders 'trunk', 'branches' & 'tags' in that -empty- repository
[3] These special folders are a SVN-specific thing, you don't have to do it this way, but it's the recommended SVN way. The repository on github has something similar but it's called "master" (git lingo)
[4] I would have moved the "ownwership" to you already, but you already have a repository by the same name on github :/ Maybe you delete it.