Awesome stuff! Great timing too. Code Search is super useful and there are a bunch of folks already going after this space. Sourcegraph, CodePilot.ai, Searchcode.com, and many more! Happy to see something so light and elegant for the use case. Good work!

Thanks, it's a simple layer on top of the existing APIs and search interfaces so it's not nearly as feature complete as those other services(that would require actually crawling and indexing). I made it just for fun but who knows, might be worth expanding on.

What's the front end? I've been thinking of building something similar, but I'm bad at front-end tech.

The frontend is reactjs. Very simple.

If someone approved their own PR in our team they would have some explaining to do, approving your own PR in an Open Source project - SMH

In many small project the owner (o small set of owners) just commit the changes without approval. In same case on person writes more than the 50% of the commits, and it's not practical to get someone to review the code.

In this case abe33 has the 75% of the commits, someone else 15% and the rest is a bunch of people with 1% or less.

Once your project gets to a certain level of users or activity, you should still be submitting PRs or MRs for comment before merger.

With our server toolkit in a project I work on, we have 2 devs and 5 active users, with the devs being 2 of those, but we still manage to at least put every change in a PR, with a minimum review and comment time of 24 hours unless it's a security issue or major bug fix.

It's not hard, and it makes you actually justify your change and have talented second eyes point out minor bugs or edge cases to you.

Direct commits are only used for version bumps for the auto build/release thingy.

Your method may be better, but there are a lot of small and medium projects in the wild that don't follow it.