git[hub] credentials do not persist across RStudio/Positron sessions (Windows machine)

[math-mcshane]

When I open a fresh Positron or RStudio session and run gitcreds::gitcreds_get(), I get

Error in `throw()`:
! Could not find any credentials
Hide Traceback
    ▆
 1. └─gitcreds::gitcreds_get()
 2.   └─gitcreds::gitcreds_parse_output(out, url)
 3.     └─gitcreds (local) throw(new_error("gitcreds_no_credentials", url = url))

So, I generate a new PAT on github.com, then use gitcreds::gitcreds_set() and then call gitcreds::gitcreds_get() and get

<gitcreds>
  protocol: https
  host    : github.com
  username: math-mcshane
  password: <-- hidden -->

When I start a fresh Positron or RStudio session, I re-run gitcreds::gitcreds_get() and once again get

Error in `throw()`:
! Could not find any credentials
Hide Traceback
    ▆
 1. └─gitcreds::gitcreds_get()
 2.   └─gitcreds::gitcreds_parse_output(out, url)
 3.     └─gitcreds (local) throw(new_error("gitcreds_no_credentials", url = url))

I've also tried using Windows credential manager and have set this multiple times:

FWIW,

Sys.info()
       sysname        release        version       nodename        machine          login           user 
     "Windows"       "10 x64"  "build 26100" "MCSHANE-UOFC"       "x86-64"     "rmcshane"     "rmcshane" 
effective_user        udomain 
    "rmcshane"      "ADLOCAL" 

And gitcreds 0.1.2

[ASNDataAnalytics]

Hey, thanks for raising this @math-mcshane. I have been using gitcreds for a while on Windows and Mac without issues (thanks very much @gaborcsardi for this great package). Today, on Windows I was prompted by {devtools} to change the token scope in the process of updating my package. After updating the GH PAT with gitcreds_set(), running usethis::get_sitrep threw the following warning:

In gitcreds_get_cache(cache_ev) : Invalid gitcreds credentials in env var GITHUB_PAT_GITHUB_COM. Maybe an unescaped ':' character?

Sys.getenv("GITHUB_PAT_GITHUB_COM") returned "protocol:https:host:github.com:username:ASNDataAnalytics:password:" (note the missing password).

After going back and forth with Claude (and deleting the credential in Windows Credential Manager) I finally added the PAT manually in the password field in Windows Credential Manager and it finally took (unlike what happened with @math-mcshane).

Don't know what would cause this, but sharing in case it's of use.

Thanks,

Kurtis