Running source code analysis on Try

TL;DR: We are leveraging the try infrastructure to perform source code analysis (linters, static analyzers, etc). You can take advantage of this to trigger other try jobs on Phabricator revisions. For more than a year, the Release Management & Quality team has been running the Code review bot

Re: Running source code analysis on Try

ree to contact me directly, or post on the Slack channel #phabricator Cheers, Bastien Abadie On Thu, May 16, 2019 at 6:18 AM Nicholas Alexander wrote: > Bastien, others, > > On Tue, May 7, 2019 at 9:38 AM Bastien Abadie wrote: > >> TL;DR: We are leveraging the try infrastruc

Re: Upcoming changes to hg.mozilla.org access

On Saturday, November 2, 2019 at 12:03:25 AM UTC+1, somb...@gmail.com wrote: > For mozilla-beta, mozilla-release, and esr... does lando know how to > land to these, or is it the case that landings on these branches are > done based on the approval flags by people other than the patch author? I'm

Update of the Code review bot: CI-breaking issues are now reported

tl;dr: The Code Review Bot will now warn you about CI-breaking issues on Phabricator Hello, We have just released a new version of the code review bot that changes slightly how lint issues are reported on Phabricator: - Issues breaking the CI are now reported as Phabricator lint results.

Code Review bot new reporting style

ho suggested this styling change, we hope you’ll enjoy this enhancement. If you have any questions regarding this change or the code review bot, you can reach us on Matrix #code-review-bot <https://chat.mozilla.org/#/room/#code-review-bot:mozilla.org>

Re: Code Review bot new reporting style

are transient. Bastien Abadie On Sat, Mar 28, 2020 at 2:20 AM Gerald Squelart wrote: > On Friday, March 27, 2020 at 11:11:46 PM UTC+11, Bastien Abadie wrote: > > The code review bot has been updated today and now publishes all issues > > found on your patches as Phabricator lint