turbo: [turborepo] Regression - ERROR run failed: error hashing package files: git error: 'git status' in REPO/packages/tsconfig had a parse error path error: Path packages/tsconfig is not parent of .editorconfig

What version of Turborepo are you using?

1.10.7

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Mac

Describe the Bug

Husky push hook runs a lint-staged task. I am getting the following error only when ran via turbo:

[turborepo] Regression -  ERROR  run failed: error hashing package files: git error: 'git status' in REPO/packages/tsconfig had a parse error path error: Path packages/tsconfig is not parent of .editorconfig

Reverting to 1.10.6 fixes this issue.

Expected Behavior

This shouldn’t happen.

To Reproduce

Wasn’t able to reproduce in a new repo, can’t share current one.

Reproduction Repo

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 5
  • Comments: 26 (8 by maintainers)

Commits related to this issue

Most upvoted comments

We’re released turbo@1.10.8 which should address this (has the fix from the canary), so I’m closing the issue. If anyone still has an issue on 1.10.8, can you please open a new issue with the specifics? Thanks!

@chris-olszewski if a specific git version is required, it might be a good idea to include that as part of the error message + mention it in the docs. It’s hard to see the connection between git and turbo, so the debug process might be hard. In fact, you might stop allowing to run turbo commands if a git version too low is found

updating git version did the trick. Thanks @chris-olszewski

I have a monorepo that has a subfold is a standalone git repo but ignored in the monorepo(do not want use git submodules because have to commit it everytime).

This error happens when the ignored git subfolder is changed and have to commit the ignored git subfolder.

I don’t believe git version is the cause of most of these issues only errors that complain about --no-renames not being a valid git flag.

I once again am asking for people who encounter this issue to include some additional information that will help me figure out what’s going on: https://github.com/vercel/turbo/issues/5447#issuecomment-1622682573

@Vintotan If you only use turbo globally (turbo isn’t listed in your project’s package.json) then npm install -g turbo@1.10.6 will do the trick.

Same here. It’s better to mention it in the docs about the connection between git and turbo. Or list the version of git that turbo@1.10.7 is competible with

@luke-concannon Can you try updating your git version?

Can confirm this in 1.10.7, working if downgrading to 1.10.6 as a temp fix @ivancuric @hta218 @luke-concannon