+ [2019-09-20T17:16:25Z] R2robot it's probably the least frequent thing a developer will do
+ [2019-09-20T17:17:54Z] zxcat in the sense of register a username make all the sense, not by using tools that the service offers.. I will try to find some way. or change to other hub lol
+ [2019-09-20T17:18:26Z] R2robot wow. lol
+ [2019-09-20T17:19:18Z] zxcat I don't use X :) that approach is not productive. https / ssh fully agree!

message no. 174658

Posted by zxcat in #github at 2019-09-20T17:11:33Z

am I sure if I am using the correct repo name ( if I am creating the repository in that commit ) I cannot fail. Username and pw is fine.
+ [2019-09-21T08:26:43Z] ASDX error. there are github admins who have greater access to us, so am wondering what would this error all of a sudden?
+ [2019-09-21T08:26:43Z] ASDX hi, i am seeing the following error ("Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected GitHub has been notified of this commit’s build result") on jenkins builds. my team has admin access to jenkins and our GitHub org, and the GitHub Admin log doesn't show any changes to the hooks since we started seeing this
+ [2019-09-21T12:09:51Z] desperek oh wow i didnt know this place existed
+ [2019-09-21T13:27:58Z] nedbat desperek: "existed" was right :)