This seems like a really cool project and could be really useful in getting to know a new codebase. How do you ensure that the output in the wiki does not contain hallucinations?

This might be a bit off-topic but is this custom-built documentation or did you use a template? I've been on the hunt for pretty documentation tools but have only come up with Mintlify.

Great work Silas! Can this also be trained on externalized sites, such as human-written docs, our web site, public-facing Google docs, etc?

Hi Silas!

Are there any plans to allow running DeepWiki against private non-GitHub repos (e.g. GitLab, Azure DevOps, etc) and keep the output private?

Hey Silas, currently deepwiki is not working for me. Yesterday it was working great and I found it really helpful, today I only see the loading page with skeletons with every prompt.It's slow and most of the times the results never come in. Previously i could see it's chain of thought now there's just the loading page with skeletons. Just wanted to let you know.

I also asked Devin a question:

Can I use a star-tree index with upserts?

I was pleasantly surprised by the answer:

https://deepwiki.com/search/can-i-use-a-startree-index-wit_a...

Briefly: "No, you cannot use a star-tree index with upserts in Apache Pinot. This is a built-in restriction that is explicitly enforced in the system."

Why This Restriction Exists

When upserts are enabled for a table in Pinot, the system explicitly checks and prevents the use of star-tree indexes. This validation happens during table configuration validation.

The code in TableConfigUtils.java explicitly enforces this restriction:

[snip]

At cursory glance, I did not detect a hallucination. The answer was true (AFAIK), clear, and objective. I also see that you can peek into other resources to get some additional contextual information.

Very impressive work.