Open EugenMayer opened 4 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
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?