6 hours ago, Shaarigan said:But if you want the person to work with your reposetory, e.g make fixes to your code, then a fork would do the trick for you. A fork is a full blown clone of your reposetory with all the files and history but into a new standalone reposetory.
Okay, so this allows me to keep my old repo, that's why I'm forking? Do I need to set up permissions for the other users? To set the fork up in Visual Studio I assume I just clone the fork and choose VS? Could I just change my repo to public to do this, because like you said I would have control over what changes I accept?
Thank you,
Josheir