#Remote Repositories | Dagger

1 messages ยท Page 1 of 1 (latest)

celest gulch
#

I ran into this with @viral frigate in github actions. I think the solution in that case was to use a PAT. Are you hitting this locally @fallen pebble ?

fallen pebble
#

yeah i'm hitting this locally

#

gh is logged in, ssh clone works

cyan ibex
fallen pebble
#

dagger call git-env --github-token=env:GITHUB_TOKEN --repo=https://github.com/myorg/myrepo#pull/123/head

#

where repo is type Directory

cyan ibex
fallen pebble
#

yeah, it works fine with public repos

#

unrelated the repo clone: for use of the gh cli inside of the dagger functions

cyan ibex
#

Can you please cehck that you have the correct info with: echo -e "protocol=https\nhost=github.com\n" | git credential fill

#

especially the password

fallen pebble
#

what should i see? it asks for username/password

cyan ibex
#

git is a beast, and the gh cli and git cli uses a lot of auth protocols and fallbacks-- Let me check the command ๐Ÿ‘€

#

can you please do : gh auth setup-git and try again the command above

fallen pebble
#

my git config has

[credential]
    helper = osxkeychain

fwiw (checking gh auth now)

#

credential fill shows my username and a pat now

cyan ibex
#

try again, it should work

fallen pebble
#

๐Ÿ™

#

I got a 403, but i guess that's because of whatever token it filled

cyan ibex
#

yep

#

I truly need to improve the error message to a docs link explaining that -- it's very host specific

#

keep me in touch ๐Ÿ™

fallen pebble
#

sheessh, how do i get it to give me an appropriate token? the gh cli is authed with my org