Closed ekohl closed 1 year ago
Hmm, can you think of a better solution than g10k always comparing the git remote at the beginning?
The other is to always set it. I haven't looked at the code, but I think git remote set-url
is a pretty cheap operation. AFAIK it's only changing .git/config
.
Consider the following config
Then I run g10k. This does what I want and we can see that:
However, now my git repo URL changes:
Again, I run g10k. This exits successfully. However, the code isn't updated. This is because the cache still points to the same remote.
Removing
control.git
and running g10k again does result in a correct git remote.