You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
Currently the rules for deciding what linters is going to be used only takes into account the extension of the file. This has several problems, one is that some files don't have an extension (for example, .gitlint), and in some other cases there are specific linters that can be used for some files. For example for travis.yml there is a specific linter, taht is only valid for that kind of files. The same happens for the phpunit configuration file, which can be called phpunit.xml.dist, in which case we only want to apply the xml linter to those files and not to all files ending with .dist.
The text was updated successfully, but these errors were encountered:
Currently the rules for deciding what linters is going to be used only takes into account the extension of the file. This has several problems, one is that some files don't have an extension (for example, .gitlint), and in some other cases there are specific linters that can be used for some files. For example for travis.yml there is a specific linter, taht is only valid for that kind of files. The same happens for the phpunit configuration file, which can be called phpunit.xml.dist, in which case we only want to apply the xml linter to those files and not to all files ending with .dist.
The text was updated successfully, but these errors were encountered: