gruntwork-io / git-xargs

git-xargs is a command-line tool (CLI) for making updates across multiple Github repositories with a single command.
https://blog.gruntwork.io/introducing-git-xargs-an-open-source-tool-to-update-multiple-github-repos-753f9f3675ec
Apache License 2.0
933 stars 63 forks source link

Error on one repository : worktree contains unstaged changes #69

Open alessandro-candon opened 2 years ago

alessandro-candon commented 2 years ago

Describe the bug When I try to apply a "command" to a list of reporitories it works perfectly on all of them except for one that return the error in attached.

Error="worktree contains unstaged changes"

To Reproduce

I can't reproduce it manually, I try to clone the project and checkout a new branch with this command git checkout -b "core/update" but I can't reproduce the error "manually".

Screenshot 2022-04-19 at 10 09 44

Expected behavior

Normal behavior, so checkout and apply the command.

alessandro-candon commented 2 years ago

Update :

I also try with a simpler command

git-xargs \
    --loglevel DEBUG \
    --branch-name test-branch \
    --repo dktunited/dktrent-core \
    --commit-message "Create hello-world.txt" \
    touch hello-world.txt
bzupnick commented 2 years ago

+1 experiencing this also

alessandro-candon commented 2 years ago

No one has find a solution?

The only way to solve this problem for me was delete and recreate the project, a little bit heavy as solution...

alessandro-candon commented 2 years ago

No one have a solution to this problem?

xaviergmail commented 1 year ago

I am also experiencing this in repos containing ~60k files after checkout. The working tree is not dirty when I clone it manually via git CLI.

anshulgargamway commented 1 year ago

We are also experiencing the same problem. Any solution for same.

jtri commented 1 year ago

I was running into this error as well. It turned out that we had two git paths with the same name but different case (ie src/utils/Sidebar.jsx vs src/Utils/Sidebar.jsx). After consolidating the paths this error went away.