You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me, the default behavior of gitcreds::gitcreds_set() is to login via a webform, and after the login, the credentials will be stored in the credential manager.
I never had to create a GH PAT and I think it makes things easier. The git-credential-manager is a recommended and official tool.
What do you think? Could this be add to the docs?
The text was updated successfully, but these errors were encountered:
I think this is really a change (or, rather, additional approach) that would need to be embraced by gh, gitcreds, gert and credentials and then, if that happened, usethis would make any necessary adjustments to its documentation and diagnostic functions.
usethis doesn't do any credential management anymore, thank god, because we can rely on gh and gert to do this (via gitcreds and credentials, respectively). So I don't see usethis leading the charge.
Does the credential you've obtained with this flow work with all the GitHub API functionality in usethis? So, not basic git operations such as clone/push/pull, but things like creating or forking a repo or creating an issue.
The section of the doc related to Github authentication (https://usethis.r-lib.org/articles/git-credentials.html) does not mention the possibility of using browser authentication instead of creating a PAT with
git-credential-manager
.For me, the default behavior of
gitcreds::gitcreds_set()
is to login via a webform, and after the login, the credentials will be stored in the credential manager.I never had to create a GH PAT and I think it makes things easier. The
git-credential-manager
is a recommended and official tool.What do you think? Could this be add to the docs?
The text was updated successfully, but these errors were encountered: