+ [5 years ago] jaakkos Now the process seems to be: the user must login first (otherwise GitHub account will not exist); then they must be manually added to organization; then within 60 minutes the LDAP-sync will sync teams
+ [5 years ago] rindolf jaakkos: this is bad and wrong bash code
+ [5 years ago] rindolf jaakkos: joke - https://www.shlomifish.org/humour/fortunes/show.cgi?id=mjd-how-to-ask-a-good-question-1
+ [5 years ago] rindolf jaakkos: do you know python?
+ [5 years ago] rindolf fannagoganna: sorry tha twas for you

message no. 175588

Posted by greyltc[m] in #github at 2019-11-01T12:23:58Z

but the message I get back is:
+ [5 years ago] gitinfo Please use SSH to talk to remote repos. http:// and git:// are completely unsecured and http:// suffers from smart webservers trying to implement policy. You can try to do "smart" https://, but it can be troublesome to configure if you do not know how (see !web_repos for simple instructions) unless your company implements a MITM attack and prevents end-to-end crypto.
+ [5 years ago] jim !ssh
+ [5 years ago] jim !ssh keys
+ [5 years ago] gitinfo Please use SSH to talk to remote repos. http:// and git:// are completely unsecured and http:// suffers from smart webservers trying to implement policy. You can try to do "smart" https://, but it can be troublesome to configure if you do not know how (see !web_repos for simple instructions) unless your company implements a MITM attack and prevents end-to-end crypto.
+ [5 years ago] jim argh. how would I add an ssh key to my github acct?