- From: Simon Fraser <smfr@me.com>
- Date: Tue, 18 Apr 2017 20:45:22 +0900
- To: Geoffrey Sneddon <me@gsnedders.com>
- Cc: Public CSS Test suite mailing list <public-css-testsuite@w3.org>
Received on Tuesday, 18 April 2017 11:46:01 UTC
lint is much too slow to conveniently run iteratively while fixing tests and I can't seem to be able to tell it just specify a subdirectory: https://github.com/w3c/web-platform-tests/issues/5598 <https://github.com/w3c/web-platform-tests/issues/5598> It's also not very helpful: https://github.com/w3c/web-platform-tests/issues/5597 <https://github.com/w3c/web-platform-tests/issues/5597> Can we fix it to allow "./lint css", or maybe have "./lint" use git status to only check files in the git index or with local changes? Simon > On Mar 1, 2017, at 11:42 PM, Geoffrey Sneddon <me@gsnedders.com> wrote: > > Can I draw people's attention to the lint script, documented at > <http://web-platform-tests.org/writing-tests/lint-tool.html>? > > Those of you committing/pushing to Mercurial, can you please ensure > you don't add any failing lints as it necessitates someone fixing them > before others contributing through GitHub can have *anything* landed? > > Thanks, > > /gsnedders >
Received on Tuesday, 18 April 2017 11:46:01 UTC