github.com/mozilla/code-review issues | Ecosyste.ms: OpenCollective

Enable responses automatically for all tests

marco-c opened this issue over 5 years ago

Nicer output for zero coverage issues

marco-c opened this issue over 5 years ago

Do not clean paths from analyzers

La0 opened this issue over 5 years ago

Push to production and enable zero coverage checker

marco-c opened this issue over 5 years ago

Don't fail if the latest coverage task was not correctly indexed

marco-c opened this pull request over 5 years ago

Create a adr recipe to get the runtime of code-review's try pushes

marco-c opened this issue over 5 years ago

Support unit test results

La0 opened this issue over 5 years ago

Do not fail on zero coverage download failure

La0 opened this issue over 5 years ago

frontend: Update dependencies.

La0 opened this pull request over 5 years ago

frontend: Update footer urls

La0 opened this pull request over 5 years ago

Add a link on uncovered files

calixteman opened this issue over 5 years ago

bot: Support NSS tasks.

La0 opened this pull request over 5 years ago

Support mozlint diff

La0 opened this pull request over 5 years ago

Use independant Taskcluster route

La0 opened this issue over 5 years ago

Use pre-commit with black

marco-c opened this issue over 5 years ago

Report warning on Phabricator when the base revision is different

La0 opened this issue over 5 years ago

Taskcluster CI/CD

La0 opened this pull request over 5 years ago

Support mozlint diffs

La0 opened this issue over 5 years ago

Pass --warnings into mozlint

Pike opened this issue over 5 years ago

Add link to Phabricator revision on try commit message

La0 opened this issue over 5 years ago

Migrate reported issues to Bugzilla

La0 opened this issue over 5 years ago

Check the author of the try push is our bot

marco-c opened this issue over 5 years ago

Code review bot cleanup

La0 opened this issue over 5 years ago

Try removing mercurial revert on failure

La0 opened this issue over 5 years ago

Support all source-test-*

marco-c opened this issue over 5 years ago

Publish issues that are outside the revision files as generic comments

marco-c opened this issue almost 6 years ago

Publish some issues as unignorable lint issues and others as comments

marco-c opened this issue almost 6 years ago

HarborMaster API should return one build only

La0 opened this issue almost 6 years ago

Use pytest tmpdir in mock_config

marco-c opened this issue almost 6 years ago

Support file renames in before/after

La0 opened this issue almost 6 years ago

Limit number of comments per file

La0 opened this issue almost 6 years ago

Problem with an automated review: Too many blank lines reported by flake8 linter

abpostelnicu opened this issue almost 6 years ago

Lint commit messages too

marco-c opened this issue about 6 years ago

Don't report issues when a new diff is available

indygreg opened this issue about 6 years ago

Problem with an automated review: spurious complaints about `noexcept`

jld opened this issue about 6 years ago

bugprone-multiple-statement-macro: will cause a lot of issues

sylvestre opened this issue over 6 years ago

performance-unnecessary-copy-initialization: Local copy is warned but it's necessary

masayuki-nakano opened this issue over 6 years ago

Code referenced by code review bot shows incorrect line numbers

marco-c opened this issue over 6 years ago

Support other projects (not mozilla-central)

marco-c opened this issue over 6 years ago

Report which clang checks are used

La0 opened this issue over 6 years ago

Close issues that have been fixed

tomprince opened this issue over 6 years ago

"Is new" attribute looks wrong on some code review issues (before/after SA)

jankeromnes opened this issue over 6 years ago

shipit_static_analysis: clang-format issues

jankeromnes opened this issue over 6 years ago

reviewbot opened two issues for one defect, and included unrelated text

mozkeeler opened this issue over 6 years ago

False positive with mozilla-implicit-constructor

staktrace opened this issue almost 7 years ago

Problem with an automated review (modernize-use-equals-default)

tomrittervg opened this issue almost 7 years ago

Run linters on the entire tree when configuration files change

marco-c opened this issue almost 7 years ago

Consider detecting issues in blacklisted code too (only for newly introduced issues)

sylvestre opened this issue almost 7 years ago

shipit_static_analysis: modernize-raw-string-literal should be suggested only on longer string

jankeromnes opened this issue almost 7 years ago

shipit_static_analysis: Improve error message `Bad implicit conversion constructor`

Yoric opened this issue about 7 years ago

Repeated/duplicate review for already-dropped issues

squelart opened this issue over 7 years ago

When we have a stack of revisions, analyze only the last one?

mstange opened this issue over 7 years ago