#Detect upstream default repo

1 messages · Page 1 of 1 (latest)

umbral wasp
#

I want to run a dagger module against a target directory and produce diff reports.
Right now I'm using generic dagger.Directory.

I'm not certain proper way to extract more of what's in the .git/config. Any quick tip on this so I don't over complicate?

north gulch
umbral wasp
#

It's a very basic usage. I'm really just wanting to replace a bunch of custom agent prompt actions with a dagger module. The module is essentially just going to dump out a different report on git changes in the branch compared to upstream. Then generate a quick summary using the LLM integration.

Copilot will call dagger and not have to do all this crunching locally making it much more rapid and portable for different OS etc.

I guess this kind of thing if we were using Claude would be a Claude skill 😉

#

Copilot offers to create a changie entry based on this content, but I'd like to speed it up by leveraging dagger for the initial legwork.

Then /changelog should be much much faster going forward with the more deterministic steps and no need to roll scripts out everywhere just call remote dagger module.

cerulean pendant
#

just going to dump out a different report on git changes in the branch compared to upstream.

does this mean basically a git diff between the local and remote git state?

#

is the target directory part of a bigger monorepo? Or is the target directory a repo on itself?