git-clone

来源： https://stackoverflow.com/questions/33104540/git-clone-no-checkout-again

来源： https://stackoverflow.com/questions/33104540/git-clone-no-checkout-again

来源： https://stackoverflow.com/questions/33104540/git-clone-no-checkout-again

来源： https://stackoverflow.com/questions/33104540/git-clone-no-checkout-again

来源： https://stackoverflow.com/questions/33104540/git-clone-no-checkout-again

来源： https://stackoverflow.com/questions/33104540/git-clone-no-checkout-again

问题 I'm trying to figure a way to prevent clone from github repository, for example, I have a private repository and some people working in that, in a company computer, each one in your team and authorization levels setted up. When I set authorization for some user on github, the repository is avaiable on his/her own github account, to see and do what want since is authorized from anywhere. How can I avoid someone to clone the repository on your own computer? Try to figure out someone is planning

问题 I'm trying to figure a way to prevent clone from github repository, for example, I have a private repository and some people working in that, in a company computer, each one in your team and authorization levels setted up. When I set authorization for some user on github, the repository is avaiable on his/her own github account, to see and do what want since is authorized from anywhere. How can I avoid someone to clone the repository on your own computer? Try to figure out someone is planning

问题 I'm trying to figure a way to prevent clone from github repository, for example, I have a private repository and some people working in that, in a company computer, each one in your team and authorization levels setted up. When I set authorization for some user on github, the repository is avaiable on his/her own github account, to see and do what want since is authorized from anywhere. How can I avoid someone to clone the repository on your own computer? Try to figure out someone is planning

问题 Foreword We have a big SVN repository (200k+ commits and hundreds of branches and tags). A big, ominous, unmaintainable, frustrating mess. To work more efficiently, about a year ago I did a git svn clone on my development machine, so I locally develop on GIT and then push to SVN. We're now thinking about splitting up the repository and move the main development branches to git, or at least to move our development branch on git. Since I have my local git repository, I wanted to do some test by