VSHN.timer #98: The Git Clone Wars

Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.

This week we’re going to learn about new and innovative ways to browse, peek, and clone Git projects, wherever they are.

1. Visual Studio Code is the text editor of the moment. Microsoft is investing lots of effort in its development, and it’s becoming hard to beat with its huge ecosystem of extensions. One of the latest is Remote Repositories, which allows developers to browse, edit, and commit to GitHub repositories directly from the editor. No more git clone!

https://marketplace.visualstudio.com/items?itemName=github.remotehub

2. But why even open your editor in the first place, when your editor runs in your web browser? This is the realization made by the github1s team: browse to any GitHub project (like our beloved Project Syn Commodore), append the 1s in between github and .com and boom, you’re editing the code in a snap.

https://github1s.com/

3. Following the lead of github1s, the team of github.surf forked the project and added a few goodies: a Google Chrome extension, a command line tool, and even GitLab support.

4. Speaking about CLI tools, are you more the terminal type? Then try git-peek. This cross-platform tool allows you to git peek any GitHub repository, and open it on your favorite EDITOR.

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

5. But none of the git clone replacements we’ve seen so far would be useful without at least a little bit of knowledge of how Git works. LJ Miranda has published this month an outstanding explanation of the Git branching model based on the… MCU franchise. Developers, Assemble!

https://ljvmiranda921.github.io/notebook/2021/06/05/avengers-git/

What is your preferred way to browse Git projects? Do you use Visual Studio Code or do you prefer other editors? Would you like to share some tips and tricks with the community? Get in touch with us, and see you next week for another edition of VSHN.timer.

PS: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.

PS²: check out our previous VSHN.timer editions about Git, GitHub, GitOps and GitLab: #10, #48, #68, and #83.