There is an api for this at https://txtrepo.com
I used it with n8n to create PRs on issues
Show HN: Dump entire Git repos into a single file for LLM prompts
11–20 of 25 posts
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#12How does this (or similar tools) differ from just a simple `cat foo bar > out`?
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#13Seems like a common itch to scratch and a good tool to scratch it with. I created 'linusfiles' and 'grabout' as tools with this. Grabout copies the last input and error message or other output to clipboard and linusfiles copies the tracked files to clipboard.
But I like the idea of tarballing it, as ndr_ suggested. I'm thinking that could be the move here.
In case anyone wanted to see my workflows https://github.com/atxtechbro/shell-tooling
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#14These are extremely common these days. Here are a few I've collected over the past few months:
- [files-to-prompt](https://github.com/simonw/files-to-prompt) (from the GOAT simonw)
- [code2prompt](https://github.com/mufeedvh/code2prompt)
- https://gh-repo-dl.cottonash.com/
- [1filellm](https://github.com/jimmc414/1filellm)
- [repopack](https://github.com/yamadashy/repopack)
- [ingest](https://github.com/sammcj/ingest)
What makes yours better?
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#15These are extremely common these days. Here are a few I've collected over the past few months: - [files-to-prompt]( https://github.com/simonw/files-to-prompt ) (from the GOAT simonw) - [code2prompt]( https://github.com/mufeedvh/code2prompt ) - https://gh-repo-dl.cottonash.com/ - [1filellm]( https://github.com/jimmc414/1filellm ) - [repopack]( https://github.com/yamadashy/repopack ) - [ingest]( https://github.com/samm…
I tried code2prompt but the interface has a quirk—even if you specified an output file, it will always put the output to the paste buffer.
Which one of these you find the best? It’s quite tempting to write one myself for something as simple as this.
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#16that's a cool project.
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#17There is an api for this at https://txtrepo.com I used it with n8n to create PRs on issues
Can you explain your n8n workflow a little bit if you don't mind? txtrepo looks interesting. I had thought about somehow combining Aider with n8n/nodered to automate a few small things, but haven't looked too much into it yet.
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#18These are extremely common these days. Here are a few I've collected over the past few months: - [files-to-prompt]( https://github.com/simonw/files-to-prompt ) (from the GOAT simonw) - [code2prompt]( https://github.com/mufeedvh/code2prompt ) - https://gh-repo-dl.cottonash.com/ - [1filellm]( https://github.com/jimmc414/1filellm ) - [repopack]( https://github.com/yamadashy/repopack ) - [ingest]( https://github.com/samm…
How did you compare the above? I'd love to see a "clear winner".
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#19These are extremely common these days. Here are a few I've collected over the past few months: - [files-to-prompt]( https://github.com/simonw/files-to-prompt ) (from the GOAT simonw) - [code2prompt]( https://github.com/mufeedvh/code2prompt ) - https://gh-repo-dl.cottonash.com/ - [1filellm]( https://github.com/jimmc414/1filellm ) - [repopack]( https://github.com/yamadashy/repopack ) - [ingest]( https://github.com/samm…
sammcj of sammcj/ingest reporting in! Funny to see my little tool pop up in comment threads.
Re: Show HN: Dump entire Git repos into a single file for LLM prompts
#20This is a similar tool I wrote for myself called "ingest". It ingests files/directories to LLM friendly markdown, estimates token usage, and can estimate vRAM usage for different models and quantisations and shows you a table highlighting which quantisation, context size and k/v cache quantisation will fit in a given (v)RAM size. - https://github.com/sammcj/ingest