Earlier quoted context omitted.
Do I still need to provide credit card info to use the promo code? No bueno.
Use privacy.com for a single use credit card number
Launch HN: Greptile (YC W24) - RAG on codebases that actually works
111–120 of 173 posts
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#1121. "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 use.
4. I couldn't see where to put the promo code.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#113It'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…
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.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#114Will it work with a large Ruby on Rails codebase?
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#115How's this different from Adrenaline or Cursor or Bloop
Cursor is different because it's really focused on augmenting the code writing experience with code gen, while we're working on code comprehension.
A good way to look at it is - Cursor replaces your IDE, Greptile replaces/augments your internal docs.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#116I just keep getting: "Error: Internal error while locating sources." when trying to talk to a repo that is green and "up to date"
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#117Love this idea and am just signed up. Thanks for the promo code! Also, I really like your blog post about shipping faster: https://greptile.com/blog/ship-faster . Shipping code is so fun that we should all be looking for ways to do more of it.
Btw, your service might be down right now. It just ingested my private repo but won't answer any questions.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#118It'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.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#119Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#120Earlier 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.