On 2024-12-09 at 16:03:49, Sergey Ivanov wrote: > Thank you for filling out a Git bug report! > Please answer the following questions to help us understand your issue. > > What did you do before the bug happened? (Steps to reproduce your issue) > 1) My remote token to git repo was expired > 2) I have git config --global credential.helper > store > and had line with given url added here > What did you expect to happen? (Expected behavior) > Git will say that token is not working > and will NOT touch credentials file. When a credential is not valid, Git invokes the helper with the `erase` argument to delete the bad credential. That's documented in git-credential(1) and gitcredentials(7). If Git didn't do that, then when it needed to prompt for a new credential, it would get exactly the same credential before, and it wouldn't work. Because most credential helpers store data in opaque stores (like the system password manager), it would be nearly impossible for the average user to understand how to clear the credential if Git didn't do it itself. > What happened instead? (Actual behavior) > Git removes whole urk from git-credentials > and says 'not token' This file is entirely managed by the credential helper. I know it seems like a plain text file you can edit by hand, and you can, but it's an implementation detail that the data is stored that way. It's not designed as a general-purpose URL store or user-owned config file that the credential helper will never edit. > What's different between what you expected and what actually happened? > I want manually change token only, noe whole URK format of which i > constantly forgetting I'm very sorry that this didn't end up working out how you expected. I think your URL may be available via `git remote -v` in your repository, which hopefully should let you recover the URL if it was associated with a remote. -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
