code-review
code-review copied to clipboard
mozilla
Automated static analysis & linting bot for Mozilla repositories
We could run it weekly. The command to run is `./manage.py cleanup_issues --nb-days=365`. https://devcenter.heroku.com/articles/scheduler
In #1415 we've added a limitation for urllib3==1.26.12, this should be removed once `requests` supports urllib3 >= 2.0.0
The backend can lists the nb of issues detected per analyzers on the last month, week, day, and detect a trend (or even a zero value). This could be exposed...
E.g. gfx/skia/skia/src/ports/SkOSLibrary_posix.cpp on https://phabricator.services.mozilla.com/D162381
It happened on https://phabricator.services.mozilla.com/D155233?id=617424. The patch was based on "701432:678444ca62ed Olli autoland Bug 1785109, mark CustomElementRegistry as multizone holder, r=mccr8", available on autoland.
If the revision has a custom policy, hence is not public, code-review will not scan it. This primarily happens on two scenarios: - Revision is tight to a bugzilla item...
The `Connected to https://api.code-review.moz.tools` text has a dark color, while the header background is already dark:  This is not accessible, as reported by the...
On https://lando.services.mozilla.com/D141589/, I see: ``` Static analysis and linting are still in progress. [D141589] Static analysis and linting did not run due to failure in applying the patch. [D141589] ```...
If we fail the Phabricator build on build errors, Phabricator will send a notification to the author. This way we don't have to use Taskcluster to send emails.
In [https://phabricator.services.mozilla.com/D128430](D128430) `code-review-bot` reported that the documentation has been touched, which is wrong but looking on the [push stack](https://treeherder.mozilla.org/jobs?repo=try&revision=e7d350dccdaef7a7bfea54de6a8e7c7af22807ca&selectedTaskRun=Uh5r3XbWRra0pi3GJYz8sQ.0) we can see that there is at least on push that...