#llm code explainer

1 messages · Page 1 of 1 (latest)

mighty sand
#

when i run that it can successfully clone the repo at that branch and it shows me the file exists but it for some reason does not have access to the file

#

llm code explainer

dawn dove
# mighty sand when i run that it can successfully clone the repo at that branch and it shows m...

either the LLM getting confused with the many tools available on the Directory type or Git type/function issues...

I'll try more manually

dagger #just using regular dagger shell

⋈ git https://github.com/dagger/dagger | branch llm | tree | file core/llm.go | contents

works

⋈ git https://github.com/dagger/dagger#llm | head | tree | file core/llm.go | contents

doesn't work - seems to be using HEAD of main even though I tried to specify branch via #llm here and via @llm in orig example seemed to work.

There are some git issues being worked on
https://github.com/dagger/dagger/issues/9328

GitHub

When cloning a git repository, the branch is accidentally confused with a tag, and we get a false tag hovering around - we should not have this. $ dagger -s core git --url https://github.com/dagger...

#

cc @pine solstice

pine solstice
#

ha

#

this is very inline with what i'm doing

#

doesn't work - seems to be using HEAD of main
you need to not use head then

#

the first URL only takes the remote, not any details of the branch

#

this is different from the syntax on the command line - but imo, the command line syntax is the hack, not the core api

dawn dove
#

Looks like this works

git https://github.com/dagger/dagger | ref  pull/9852/merge | tree
pine solstice
#

it would be possible to change it to do that if we wanted i guess

#

but HEAD is a symref in the remote repository

#

it's not something that can really be overridden