I believe the point of these tools is to be UNIXy, doing one thing well, and delegating the rest to other tools you already use. The script just downloads source code and drops you into an editor. Presumably, if you're a developer, you already have your editor set up for handling source code directories.
for the core functionality, the tool pretty much does that, although I am thinking of adding trending repos and things as such.. and any other features that other folks have in mind, keeping the core utility of the tool as opening a repo in your editor
11 comments
[ 1.1 ms ] story [ 48.3 ms ] threadFuture improvements I am looking at is to add a search for trending remote repos and some caching mechanism
Thread about git-peek (which the author here cites as inspiration) from a few days ago: https://news.ycombinator.com/item?id=26108039
And the top commenter there created a cute bash 10-liner that basically implements the same functionality: https://git.sr.ht/~alexdavid/dotfiles/tree/master/bin/git-pe...
Above only works on vim. But has the advantage of working within vim, so no need to open a new instance, and with no external dependencies beyond git.
This latest one (repo-peek) explicitly only works with github and gitlab
Knowing me, I'd close out and then realize I needed to search something else, etc.
Yay working with academic researchers.