Open EugenMayer opened 9 months ago
AFAICS the problem is, that global gitignore definitions are ignored by the cr, means if there is something in the repo, that is ignored by ~/.gitignore
but not by the .gitignore
file in the repo itself, one gets the above rebase issue with unstaged changes.
We should at least state this in cr - using ~/.gitignore
is not uncommon
I'm have the same issue with v1.6.1
.
I have no idea why.
Loading index file from git repository .cr-index/index.yaml
Preparing worktree (detached HEAD 61f39d8)
HEAD is now at 61f39d8 updated .gitignore
Found azure-group-controller-1.0.0.tgz
Extracting chart metadata from .cr-release-packages/azure-group-controller-1.0.0.tgz
Calculating Hash for .cr-release-packages/azure-group-controller-1.0.0.tgz
Updating index .cr-index/index.yaml
error: cannot pull with rebase: You have unstaged changes.
error: Please commit or stash them.
Error: exit status 128
After upgrading from 1.4 to 1.6.1 i know get a rebase issue when pushing the index. I do not have any un pushed changes.
I went so far removing the repo locally and cloning it from scarch and trying to release the charts to the index, but it happened again
Do i miss something?