Their default search still sucks, IMO. But the one I mentioned is comparable to Google’s internal CS.
In some ways it’s even worse now, because it seems to only build an index of the repository on the first search, when I need a result now.
That will load a web version of VS Code, and you can then use the search from there.
It uses a temp directory, and deletes it when you close your editor.
Having it as button in browser seems cool but also horribly insecure...
#!/usr/bin/env bash
# Expects a single argument: git-peek://<path>
# Example: git-peek://https://github.com/Jarred-Sumner/peek
kitty --single-instance --detach -e zsh -c "source ~/.zshrc; git peek $1"
You can set it up to do anything you like.Is there a reasonably legitimate reason to stop using this?
My understanding is that GitHub's on premises version doesn't have any plans to include the new code search functionality.
It only makes it irrelevamt if all your code is hosted on Github.
I'm quite tired of Github-proprietary solutions being hailed as the "industry norm." Or vendors like shipping products and integrations that only work with Github. Git is a decentralized protocol; please treat it like one.
So complaining about Github proprietary tools and at the same time supporting Apple and Google for doing the same is a bit contradictory. Should be using an open OS and browser.
From a software eng infra standpoint, in general, ok. But we can look elsewhere.
In the mobile space, for example, it's hard to deny iOS & Android, Appstore & Google Play.
In terms of privacy, the internet is a complete failure with Chrome, Google Analytics, etc.
A large chunk of the most relevant software businesses go to the extent of mandating developers to use Apple products. I experienced this myself, when I wasn't allowed to use a PC running Linux for "security reasons". Like if Apple OS is safer than Arch. That's a big point of failure, in my opinion...
1. GitHub isn’t free, especially for large private organisations 2. Source graph has much better search functions compared to GitHub
The recent rewrite of github search has probably made sourcegraph irrelevant. If you may recall, original github search used almost the most horrible algorithm possible. It dropped all punctuation and spacing and just searched for identifiers. No patterns allowed, no quoting allowed. One of the only meta-arguments was filename:xyz.
Now that github has improved its basic search functionality, sourcegraph might be doomed.
I used sourcegraph at Lyft which (at the time) had unlimited money to waste on software tools, and installed the open-source version at Databricks but nobody cared.