code-review icon indicating copy to clipboard operation
code-review copied to clipboard

Automated static analysis & linting bot for Mozilla repositories

Results 160 code-review issues
Sort by recently updated
recently updated
newest added

Bumps [eslint-plugin-promise](https://github.com/eslint-community/eslint-plugin-promise) from 6.4.0 to 6.6.0. Release notes Sourced from eslint-plugin-promise's releases. v6.6.0 6.6.0 (2024-07-21) Bug Fixes always-return: treat process.exit() or process.abort() as an acceptable "return" (#493) (f368c5a) Features add...

frontend

As the analyzers will use the new default format, we should deprecate the different tasks. We'll also need to support current & new payload for a time (while all the...

bot
teklia-2024

E.g. our web dyno might not need to be a performance dyno, now that we have worker dynos with the Mercurial clones.

teklia-2024

In order to actually use the work done in https://github.com/mozilla/code-review/pull/1517, we need to enable local cloning. In order to enable local cloning, we need to make sure we don't clone...

The new https://hg.mozilla.org/releases/mozilla-esr128/ should get code-review support.

https://github.com/magicstack/uvloop

enhancement

It would be nice to treat compiler warnings as SA/linting issues and publish them on Phabricator. @abpostelnicu would it be feasible to collect them from the coverity job, like we...

Right now we're only reporting the pass/fail status, we could instead report a few more data about them: https://phabricator.services.mozilla.com/conduit/method/harbormaster.sendmessage/.

enhancement
events

We can probably use Push Health from Treeherder, CC @camd.

events