[08:33:46] <Urbanecm>	 tgr: would work too
[08:34:40] <Urbanecm>	 I currently make an API request to get email address, send an email and throw away the email address - so i just store tokens that can be easily revoked by the user should they want to do so
[09:17:41] <tgr>	 https://phabricator.wikimedia.org/T241039
[15:47:37] <anomie>	 Do we now have both "SonarQube Bot" and Jenkins mwcore-codehealth-patch doing the same thing?
[15:48:08] <anomie>	 e.g. https://gerrit.wikimedia.org/r/c/mediawiki/core/+/559029#message-5d60e59ef08e0e902117a215df83e50dad31f9f3 and https://gerrit.wikimedia.org/r/c/mediawiki/core/+/559029#message-e716c1be8df5a1c8d5865307b1fe38dbed573a1f
[16:36:57] <Reedy>	 Was there any comms on what that sonarqube bot is actually doing?
[16:41:22] <James_F>	 Reedy: Not yet.
[16:41:48] <James_F>	 anomie: The plan is for the SQ bot to replace the job, I believe, but as Reedy points out, there's been no communications yet.
[21:24:25] <kostajh>	 T240935 has some notes about the problem.
[21:24:25] <stashbot>	 T240935: Remove independent code health pipeline and integrate into test pipeline - https://phabricator.wikimedia.org/T240935
[21:25:06] <kostajh>	 SonarQube Bot does the same thing the codehealth pipeline did/does; report on what SonarQube thinks of the code in a patch. The bot is able to post specific comments though, while the pipeline could only say pass/fail.
[21:49:20] <James_F>	 Because jenkins sucks, roughly.
[21:58:43] * Reedy feigns shock
[21:59:48] <kostajh>	 Jenkins, or Zuul? ¯\_(ツ)_/¯
[22:37:16] <paladox>	 It'll be jenkins :P