`git ls-files -m -o` fails when upgrading from v5

After upgrading I get a error when listing modified files. I assume this might be something to do with the assets change but not sure the correct way to fix it. The build requires no extra assets other than the package.json and CHANGELOG.md. I cannot reproduce it locally, so not sure what is happening. My hunch is that CircleCI is somehow enabling the modules inside the node_modules was wondering if you peeps have a better idea. See the build failure and the project

[Semantic release]: An error occurred while running semantic-release: { Error: Command failed: git ls-files -m -o
fatal: Not a git repository: node_modules/art/lib/slick/../../.git/modules/lib/slick


    at makeError (/home/circleci/repo/node_modules/execa/index.js:172:9)
    at Promise.all.then.arr (/home/circleci/repo/node_modules/execa/index.js:277:16)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  code: 128,
  stdout: '',
  stderr: 'fatal: Not a git repository: node_modules/art/lib/slick/../../.git/modules/lib/slick\n',
  failed: true,
  signal: null,
  cmd: 'git ls-files -m -o',
  timedOut: false,
  killed: false,
  pluginName: '@semantic-release/git' }

Have just stuck with v5 for now…

[pvdlg]

It seems using the option --directory solve the problem. I have to check if it doesn’t have any negative impact.

[pvdlg]

Ideally I’d like to find a way to prevent the issue in this module. If you have any idea on how to run git ls-files -m -o ignoring .gitmodules let me know.