search

DIDSR / iMRMC

iMRMC: Software to do multi-reader multi-case analysis of reader studies
http://didsr.github.io/iMRMC/
Other
22 stars 17 forks source link

Should we change from HTTPS to SSH access to github #93

Closed brandon-gallas closed 8 years ago

brandon-gallas commented 8 years ago

I really like tortoiseSVN. SVN is a different version control method/software. tortoise nicely integrates the work that I do.

To Brandon From Qi: Here are some information about github SSH. Please let me know if you need any additional information. Thank you.

Answer about 4 questions.

  1. why your recommend HTTPS

Many company firewalls and public internet hotspots block port 22, which is the port that SSH communicates over. Attempting to use SSH in those networks will fail.

  1. what is the main difference between them.

They are both secure communication protocols. The main difference is how you access them. HTTPS is accessed using your username and password, whereas SSH is accessed by adding a key to your local computer that is paired with your GitHub account.

  1. Does SSH safer than HTTPS, why?

SSH offers encryption, which some people consider safer. You can read more about the differences in the protocols here:

https://git-scm.com/book/ch4-1.html

  1. Now we using, TortoiseSVN to clone repository though HTTPS. Could we do the same thing for SSH?

No, we're only able to support TortoiseSVN over HTTPS: https://help.github.com/articles/support-for-subversion-clients/

My summary about how to use communicate with SSH. We should use any Git-based tool to clone and commit through SSH. GitHub Desktop is a good start point https://desktop.github.com.

After clone by the software, we could find the URL information in “gear sign” - > Repository Settings -> Remote. But we can’t edit it at here. We should do it via the command line. We should right-click on the repository name and select "Open in Git Shell" and then run the following command:

git remote set-url origin + SSH URL.
(Example: git remote set-url origin git@github.com:qigongFDA/Spoon-Knife.git )

GitHub Desktop will help show us the conflicts, but we will still need to resolve them via the command line: https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line/

Regards, Qi

brandon-gallas commented 8 years ago

I created this issue to archive your response. Thanks Qi. Now I close the issue.