Troubleshooting: Prompts for password when validating with an existing clone #97

New issue

Open

opened 2024-06-29 19:34:29 +01:00 by kemitix · 0 comments

kemitix commented

2024-06-29 19:34:29 +01:00

Owner

If the authentication token has been changed, then you may be prompted for the password.

Password for https://kemitix@github.com:

This could be because the bare clone that had been created previously includes the previous git token in it's config file.

You can either delete the local clone (in ${storage.path}/${forge.alias}/${repo.alias}, or update the token in the config file in that directory.

If the authentication token has been changed, then you may be prompted for the password. ``` Password for https://kemitix@github.com: ``` This could be because the bare clone that had been created previously includes the previous git token in it's `config` file. You can either delete the local clone (in `${storage.path}/${forge.alias}/${repo.alias}`, or update the token in the `config` file in that directory.

kemitix added the

Kind/Documentation

label 2024-06-29 19:34:29 +01:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: kemitix/git-next#97

No description provided.