Closed
Bug 1502068
Opened 6 years ago
Closed 2 years ago
Configure `hg fix` usage in configwizard
Categories
(Developer Services :: Mercurial: configwizard, enhancement)
Developer Services
Mercurial: configwizard
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sheehan, Unassigned)
References
(Blocks 1 open bug)
Details
A few Google employees have recently upstreamed the `fix` Mercurial extension. From the help output for the extension: "Provides a command that runs configured tools on the contents of modified files, writing back any fixes to the working copy or replacing changesets." You can run `hg --config extensions.fix= help -e fix --verbose` on Mercurial 4.7+ for more details.
I think it would be cool if configwizard would check for valid Mercurial versions and set up `hg fix` to work against our static analysis/linters if the extension is supported. The output of `./mach lint --list` shows we have some support for:
- 'cpp-virtual-final'
- 'shellcheck'
- 'py3'
- 'test-disable'
- 'py2'
- 'eslint'
- 'codespell'
- 'wpt'
- 'yaml'
- 'mingw-capitalization'
- 'flake8'
I believe we also use clang-format and rustfmt to varying degrees across the codebase.
Comment 1•6 years ago
|
||
Bug 1188202 is tracking rewriting the Firefox repo with clang-format to use Google's style convention.
Blocks: clang-format
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•