Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on one repository : worktree contains unstaged changes #69

Open
alessandro-candon opened this issue Apr 19, 2022 · 7 comments
Open
Labels
bug Something isn't working

Comments

@alessandro-candon
Copy link

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 alessandro-candon added the bug Something isn't working label Apr 19, 2022
@alessandro-candon
Copy link
Author

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
Copy link

+1 experiencing this also

@alessandro-candon
Copy link
Author

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
Copy link
Author

No one have a solution to this problem?

@xaviergmail
Copy link

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
Copy link

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

@jtri
Copy link

jtri commented Apr 26, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants