mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-25 05:41:12 +00:00
787fff6a51
As of this patch, any lint issue at the "warning" level will *only* be displayed if --warnings is passed in. This gives us some flexibility to track issues that are "recommended to fix" but that aren't required (aka don't cause a backout). I think it would be ideal if the reviewbot ran with warnings enabled, and CI ran without warnings. This way these issues will be surfaced to developers (and hopefully get fixed prior to landing), but developers will always be able to ignore them if the situation warrants it. Since the last change converted everything to use errors, this patch should be a no-op for now. However as we move forward (and potentially decide that certain types of lint issues should result in a backout), this feature will start seeing more and more use. Depends on D3820 Differential Revision: https://phabricator.services.mozilla.com/D3821 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
l10n/fluent_migrations | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
safety | ||
mach_commands.py | ||
moz.build | ||
README |
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025