+ [2015-10-15T22:57:35Z] ELLIOTTCABLE like. I shouldn't get a prompt. Why would `git push` be trying to do *username/password* authentication for GitHub?
+ [2015-10-15T22:59:24Z] Seveas ELLIOTTCABLE: ls -lad ~ ~/.identity.insecure
+ [2015-10-15T23:06:45Z] ELLIOTTCABLE Seveas: figured it out, actually. Discovered GH had a help-article on this.
+ [2015-10-15T23:06:55Z] ELLIOTTCABLE I always thought that the https URLs were ‘fake,’ and actually resolved over SSH with identities.
+ [2015-10-15T23:07:27Z] ELLIOTTCABLE Turns out that somehow my *actual GitHub password* somehow snuck into my OS X keychain, and was being used for HTTPS authentication; so now that half my freaking repos are cloned via HTTPS, I have to re-configure them to *actually* use SSH.

message no. 116252

Posted by solatis in #github at 2015-10-15T06:08:32Z

ok, so, if I want to refer from a commit to an issue in a *parent* repo (as in, the repo i forked to fix the issue), i can just use #123 issue number, right ?
+ [2015-10-16T02:07:50Z] jameswhite technicalpickles: you are the best, man
+ [2015-10-16T02:13:00Z] jameswhite technicalpickles get in on +security ops for the bluejeans we've got open for thor'sday at the bikeshed
+ [2015-10-16T03:06:22Z] ne1 hello