git-peek VS repo

Yesterday I found out about git-peek (https://github.com/Jarred-Sumner/git-peek). Instead of describing how satisfying it is to use, here is a GIF: https://imgur.com/a/cT8zAha

You might find git-peek useful:

https://github.com/jarred-sumner/git-peek

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

You just clone the repository onto that computer with git clone https://github.com/name/repo. It should work automatically

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).

you can install a package with git like using pip install git+https://github.com/name/repo