Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
repo
-
Sourcegraph is no longer Open Source
The button on the browser just navigates to the URL `git-peek://https://github.com/name/repo`. How your system handles this git-peek protocol is completely up to you. While the git-peek package does offer to setup a handler for this custom git-peek protocol, I went ahead and set it up manually. Now, my system calls this bash script whenever it encounters the git-peek protocol:
#!/usr/bin/env bash
-
Syncing between personal MacBook and a Work Windows computer
You just clone the repository onto that computer with git clone https://github.com/name/repo. It should work automatically
-
When i push from my computer, i'm never asked for my password, which is good but i don't understand why.
I have a /home/.ssh/ directory, with id_rsa and id_rsa.pub inside, and I think that's the reason i don't have to manually authenticate, however every post i found about how to use this method also explains that i have to associate the key with my account or repo on github, which i haven't done (at least, when i go to my github setting there's aren't any SSH keys registered), and to use SSH-compatible URLs for my repos, which i'm not doing neither (i'm just using the very normal https ones, like https://github.com/name/repo).
-
Updating py-cord to 2.0
you can install a package with git like using pip install git+https://github.com/name/repo
- A list of "curl pipe in to shell" to install projects
zoekt
-
Code Search at Google: The Story of Han-Wen and Zoekt
Russ Cox' trigram approach uses document IDs for the posting list, which makes the index much smaller, but gives less precise (ie. slower) matching. This is mentioned in the design doc at https://github.com/sourcegraph/zoekt/blob/main/doc/design.md....
-
Cody – The AI that knows your entire codebase
https://github.com/sourcegraph/zoekt seems to be doing a fair but of heavy lifting for Cody.
-
Sourcegraph is no longer Open Source
What is a good open-source system for code search if I want to plug 100 or so git repos into it and have it available over the web? GH search is not desirable because it would search too broadly and would not cover repos on Gitlab etc.
I looked at the Debian code search [1] in the past, but for some reason thought it required a bit too much effort and didn't complete my investigation of it. Though [2] looks pretty approachable.
Sourcegraph mentioned Zoekt [3], but I am not sure how usable it is. If it was pretty good, why did Sourcegraph OSS exist?
Finally, from all the discussion how Sourcegraph OSS was very behind in the past few years, I guess there is no serious plan to fork it?
[1]: https://github.com/Debian/dcs
[2]: https://github.com/Debian/dcs/blob/main/howto/building.md
[3]: https://github.com/sourcegraph/zoekt
What are some alternatives?
basher - A package manager for shell scripts.
livegrep - Interactively grep source code. Source for http://livegrep.com/
sourcegraph-release-train - Sourcegraph Opensource build
cody - AI that knows your entire codebase
git-peek - git repo to local editor instantly
hound - Lightning fast code searching made easy
dcs - Debian Code Search (codesearch.debian.net) is a search engine that searches through all the 130 GB of open source software that is included in Debian. Supports regular expressions!
mozsearch - Mozilla code search website. (Please file bugs in bugzilla at https://mzl.la/2YtXmoN)
bpkg - Lightweight bash package manager
lsp-cody - A Client to Connect to the Cody LSP Gateway