+ [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-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-21T12:09:51Z] desperek oh wow i didnt know this place existed
+ [2019-09-21T13:27:58Z] nedbat desperek: "existed" was right :)

message no. 174671

Posted by ASDX in #github at 2019-09-21T08:26:43Z

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-23T08:59:38Z] david2 hi to all just a small question im trying to create a release and inject a name in the .gz right now its always 1.0.tar.gz thanks for your help
+ [2019-09-23T09:23:44Z] R2robot You didn't ask a question
+ [2019-09-23T21:56:22Z] wltjr greetings, rookie PR merge ?, merged a PR but it did not close as merge as I did before, plz help ty :) -> http://dpaste.com/1HNF79S
+ [2019-09-24T21:29:12Z] kevr are user forks shallow?
+ [2019-09-24T21:36:31Z] jhass nope