David Sveningsson

I cant reproduce this issue, can you create a minimal reproduction repo showing the configuration yielding this issue? Take a look at [@html-validate/eslint-config](https://gitlab.com/html-validate/eslint-config), it runs with NPM workspaces and this...

That would certainly be possible, anything in particular you would like it to show?

I think it would be nice if it displayed: * Which packages will be bumped (even better if it could describe why it is being bumped: "direct modifications", "bumped by...

I was going to write something like "isn't `name` required" but today I learned it's not required if the package isn't published as would be the case with a monorepo...

> Is this the first `git` operation run by _lint-staged_? Where is `git` installed, seems like your environment is not finding it as the error is `ENOENT`. No, third and...

``` $ git --version git version 2.45.2 ```

Yes, that works for me: ``` lint-staged:execGit Running git command [ 'rev-parse', '--show-cdup' ] +0ms lint-staged:resolveGitRepo Resolved git directory to be `C:/path/to/repo` +186ms lint-staged:execGit Running git command [ 'rev-parse', '--absolute-git-dir'...

``` $ git rev-parse --path-format=absolute --show-toplevel /c/path/to/repo $ stat $(git rev-parse --path-format=absolute --show-toplevel) File: /c/path/to/repo Size: 0 Blocks: 24 IO Block: 65536 directory ... ``` I was experimenting a bit...

> I think I finally managed to reproduce the issue in GitHub Actions in #1448, by installing `git` via the MSYS2 setup action. Using the default binary included in the...

After I put `/c/Program Files/Git/bin` first in PATH to use Git for Windows instead the issue goes away so at least I can use that as a workaround for now.