Dotfiles still being ignored with version 6.8.0

Tell us about your environment

• Node version: v13.7.0
• npm version: v6.13.6
• Local ESLint version: v6.8.0 (Currently used)
• Global ESLint version: Not found

What parser (default, Babel-ESLint, etc.) are you using?

default

Please show your full configuration:

Configuration

const defaults = {
    "env": {
        "browser": true,
        "es6": true
    },
    "extends": "eslint:recommended",
    "globals": {
        "Atomics": "readonly",
        "SharedArrayBuffer": "readonly"
    },
    "parserOptions": {
        "ecmaVersion": 2018,
        "sourceType": "module"
    },
    "rules": {
    },
}

module.exports = {
    ...defaults,
    overrides: [{
        files: ['.my-dotfile.js'],
        ...defaults
    }]
};

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

Dot files are being ignored, even when explicitly set in the overrides section. See config.

yarn run eslint .my-dotfile.js # ignores file despite explicitly naming it
yarn run eslint .              # ingores file too despite being explicitly set in overrides section in config

What did you expect to happen?

The .my-dotfile.js file should have been linted

What actually happened? Please include the actual, raw output from ESLint.

It did not lint the file

/home/ayzing/workspace/repro-eslint-dotfiles-not-working/.my-dotfile.js
  0:0  warning  File ignored by default.  Use a negated ignore pattern (like "--ignore-pattern '!<relative/path/to/filename>'") to override

✖ 1 problem (0 errors, 1 warning)

Are you willing to submit a pull request to fix this bug?

Not at this time. Here’s a sample repo to help with the debugging.

[kaicataldo]

overrides still respects ignore patterns, so you’ll want to follow the suggestion given in the error message. Alternatively, you can use an .eslintignore file or by specifying ignorePatterns in your configuration.

Unrelated to this, but overrides are merged into the top-level config (the intention is to allow users to override the base config for specific files), so you don’t need to merge defaults into the overrides entry.

[thescientist13]

Great, and good to know @kaicataldo ! And now also answers a very important question… who lints the linters? (spoilers: it’s also the linters 😄 )