It's cool to see tools like this. I ran into some issues though: 1. "We will email you"... "once the repositories have finished processing" Not sure you're supposed to do that without consent, when the intent was just to connect GitHub! Email use is supposed to be opt-in. 2. My tiny repo ( https://github.com/lukestanley/ChillTranslator ) won't load. 3. The UI for selecting a GitHub repo is hard to find and fiddly to…
1. Good point, didn’t think of that. We could make it a checkbox 2. Sadly, AWS just went down, absolute scramble at the office 3. Fiddly is the right word, we just changed it a couple days ago. Will make it cleaner. 4. You should only need that if you’re planning to upgrade, so you can click on the upgrade button and you should see a “Add promotion code” option on the left of checkout.
Launch HN: Greptile (YC W24) - RAG on codebases that actually works
121–130 of 173 posts
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#122Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#123Earlier quoted context omitted.
1. Good point, didn’t think of that. We could make it a checkbox 2. Sadly, AWS just went down, absolute scramble at the office 3. Fiddly is the right word, we just changed it a couple days ago. Will make it cleaner. 4. You should only need that if you’re planning to upgrade, so you can click on the upgrade button and you should see a “Add promotion code” option on the left of checkout.
I like to use different email addresses for different services. Please just ask me for an email address to use instead of using the one on github.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#124Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#125Earlier quoted context omitted.
When a commit code is pushed to that remote branch
OK, then why would that be crazy for local when it is the trigger for non-local?
That said, I think you're right and we might be overestimating the lift there. Will look into it more.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#126I'd love to try it, but pretty much all my repos are >10mb. It's not because there is that much code, but because I am doing bioinformatics and the test files (for the unit tests) inflate the repo size. It would be great if there was a way to test it on just 1 large repo for perhaps a week or something, because I balk at the idea of spending $20 a month on something that I don't even know works well. This is importan…
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#127I'd love to try it, but pretty much all my repos are >10mb. It's not because there is that much code, but because I am doing bioinformatics and the test files (for the unit tests) inflate the repo size. It would be great if there was a way to test it on just 1 large repo for perhaps a week or something, because I balk at the idea of spending $20 a month on something that I don't even know works well. This is importan…
As an aside I suggest using dvc. It stores only metadata of large files in the got repository while maintain a separate data repository. The data repository can also be synced with cloud storage like AWS. It really helps manage code better without raw data
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#128Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#129Earlier quoted context omitted.
This sort of tech will just spur developers to put proper comments in their code, which they should have been doing in the first place.
Didn't even think about that, hopefully it turns out to be true.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#130Earlier quoted context omitted.
> The latter is typically the realm of requirements, design documentation, and possibly test plans. You forgot one of the biggest spots for "why" documentation... git commit messages, where the point is to say why you made this change. Maybe taking into account the commit messages around the code in question would help.
"Initial commit" is my goto commit message. Still a great idea, though. Ingesting all data from JIRA may be beneficial as well.