Fresh checkout leaves repo with changes

[andriy-bulynko]

Please see this repo for an example: go-git-test

I'm attempting to check out a tag and it leaves the repo "dirty". Am I doing something wrong?

On OSX it prints:

Not currently on any branch.
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

        deleted:    manifests/base/transformers/mongoDbUri/kustomization.yaml
        deleted:    manifests/base/transformers/mongoDbUri/selectivepatch.yaml

no changes added to commit (use "git add" and/or "git commit -a")

On Windows it prints:

Not currently on any branch.
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   ci/scripts/check-pods.sh
        modified:   ci/scripts/cleanup-namespaces.sh
        modified:   ci/scripts/cluster-login.sh
        modified:   ci/scripts/common-func.sh
        modified:   ci/scripts/delete-namespace.sh
        modified:   ci/scripts/export-pod-logs.sh
        modified:   ci/scripts/helm-init.sh
        modified:   ci/scripts/install-namespace.sh
        modified:   ci/scripts/qliksense-generate-certs.sh
        modified:   ci/scripts/qliksense-install.sh
        modified:   ci/scripts/qliksense-simple-oidc.sh
        modified:   ci/scripts/run-system-test.sh
        modified:   ci/scripts/watch-pods.sh
        modified:   preflight.sh

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        deleted:    manifests/base/transformers/mongoDbUri/kustomization.yaml
        deleted:    manifests/base/transformers/mongoDbUri/selectivepatch.yaml

[cdlewis]

I'm seeing this behaviour too. It's very confusing.

[noerw]

Same here, makes this lib unusable for non-bare repos.

In my case (mostly?) files are affected, that were covered by .gitignore in one revision, but not the other.

[kamaln7]

I'm running into the same issue as @noerw — the current revision includes some files in .gitignore and the second revision that I'm checking out removes them from .gitignore and checks them into a commit. The result is that these files are missing after checking out the second revision.

As a workaround, I found that resetting the work tree after the checkout returns the missing files:

err = workTree.Reset(&git.ResetOptions{
	Mode: git.HardReset,
})

This works for my use case but not necessarily others.

[github-actions]

To help us keep things tidy and focus on the active tasks, we've introduced a stale bot to spot issues/PRs that haven't had any activity in a while.

This particular issue hasn't had any updates or activity in the past 90 days, so it's been labeled as 'stale'. If it remains inactive for the next 30 days, it'll be automatically closed.

We understand everyone's busy, but if this issue is still important to you, please feel free to add a comment or make an update to keep it active.

Thanks for your understanding and cooperation!