+ [2020-03-31T23:40:25Z] R2robot if that's the case, I wouldn't let them get away with answers like that. I was in a similar situation 1 provider.. DSL 8 down, 1 up was the top speed.. hehe
+ [2020-03-31T23:41:42Z] R2robot when I had an issue I had to keep calling and 'escalating' until I finally got put in touch with an actual network engineer who confirmed everything I was talking about.. and actually put some fixes in place.
+ [2020-03-31T23:42:11Z] R2robot the level 1 helpdesk ding dongs just don't know much about anything that isn't in their little help screen
+ [2020-03-31T23:45:08Z] BMO-noire haha, good to know that's a potential solution
+ [2020-03-31T23:45:17Z] BMO-noire I don't think I have the patience for it today, but maybe

message no. 178740

Posted by tomkralidis in #github at 2020-03-31T02:30:48Z

nm, looks like legacy service migration was needed. Sorry for the noise
+ [2020-04-01T16:22:47Z] cornfeedhobo I'm stumbling through the API this morning. Asking in case anyone has solved this before me.
+ [2020-04-01T16:23:07Z] cornfeedhobo Does anyone know how I might figure out what branch or commit a branch came from?
+ [2020-04-01T17:10:12Z] BtbN What do you mean, came from?
+ [2020-04-01T17:10:19Z] BtbN git does not track that
+ [2020-04-01T17:10:29Z] BtbN you can find the common ancestor, if that's what you mean