Note the latest GitSense version doesn't include branch level code searching. I'm still testing this out, and I'll be releasing another GitSense update very soon, which also includes support for BitBucket.
And sometime next week, I'm going to start looking for beta testers for my indexing engine, which is what makes all of this possible. If you have 10,000 or less commits in your repository, you'll be able to install and use the indexing engine for free. However the free version won't include diff indexing, as that greatly increases the number of moving parts.
I don't want to pooh-pooh anyone's hard work--please don't misunderstand me--but I am legitimately curious: why put so much effort into building a house of cards upon a foundation of shifting sand? Your project is completely dependent on GitHub's reliability, integrity, and goodwill. It could implement its own version of your enhancements and render yours obsolete. Arguably, it should do that, because what's the point of relegating useful enhancements to third-party products?
So doesn't that mean that your project is living on borrowed time? Why not build upon an open platform instead, one that you can control, one that can't be ripped out from under you?
Again, I don't mean this as criticism, I'm just very curious, because I don't understand.
You have a valid point, but what isn't obvious is my technology isn't really dependent on GitHub. The only thing that can cripple me is Git becoming less vogue. There are two parts to my technology:
- There is the front end which is 100% JavaScript and this is important since it allows me to build on top of existing web solutions like GitHub
- There is the indexing engine which was insanely hard to develop and is what makes my solution unique.
I've attached some screenshots that shows how I'm using my JavaScript technology to integrate with Bitbucket here:
I've also uploaded some screenshots that shows how I monitor/manage indexing. Right now, my indexing engine can easily process 10s of thousands of repositories with millions of branches on a single machine. The indexers are designed to scale horizontally and developing them was insanely hard and that's what I'm really selling. There is a reason why GitHub stopped indexing commits a few years ago. And why Bitbucket has a 5 year old ticket about code searching:
Should the worst happen and I get shut out by GitHub and Atlassian, there is always GitLab, Gogs, etc. For now, I'm more than happy to build on top of GitHub and ensuring my solution works with their Enterprise offering.
The browser extension is nifty, but Connect provides a proper API for embedding custom views in the Bitbucket UI if you want something a bit more robust (i.e. it will still work even if we decide to change the DOM at some point in the future).
I looked at Bitbucket Connect, but it looks like everything is done via iframe for obvious security reasons. This doesn't appear to be the case with Bitbucket server.
Somebody from Atlassian has reached out to me and I'll get back to them next week to see what can be done to get this working with the Connect framework.
The same can be said of anything built on top of the Twitter's and Facebook's of the world. Of course there is risk, but there is also some reward there too that is possible. It is a good question, but almost any API published by a corporation has risk of it being ripped out from under you.
Just an FYI. I've implemented commits search among other things for GitHub. You can learn more about it here:
http://gitsense.github.io/
Note the latest GitSense version doesn't include branch level code searching. I'm still testing this out, and I'll be releasing another GitSense update very soon, which also includes support for BitBucket.
And sometime next week, I'm going to start looking for beta testers for my indexing engine, which is what makes all of this possible. If you have 10,000 or less commits in your repository, you'll be able to install and use the indexing engine for free. However the free version won't include diff indexing, as that greatly increases the number of moving parts.