Geoff Alexander
Geoff Alexander
I was also having this problem. I had two `git-lfs.exe` binaries which I replace with the latest Git LFS build: ``` C:\WINDOWS\system32>where git-lfs C:\Program Files\Git LFS\git-lfs.exe C:\Program Files\Git\cmd\git-lfs.exe ``` Even...
I found workaround that works for me. What I did is to use a **dollar** shell variable to escape the Tekton parameter: ``` --- apiVersion: tekton.dev/v1beta1 kind: Task metadata: name:...
Any update on a fix?
I'm going to look at fixing this bug. @newren I don't seem to have the authority to assign this issue to myself. Please feel do this for me (or give...
I found what looks to be a workaround to this bug at [Rewriting git history simply with git-filter-repo](https://andrewlock.net/rewriting-git-history-simply-with-git-filter-repo/). The workaround is to add the `--replace-refs delete-no-add` option ### Without the...
I asked a similar question in Discussion #553 and am still interested in an answer.
This problem looks to be an example of "unexpected" behavior that can occur when the new name in `--path-rename ` already exists in the commit history. In the above scenario,...