Changelog

lazygit is a simple terminal UI for git commands, written in Go with the gocui library. They had me sold at "lazy" 😉

Right now, the only way to sign your git commits is to use PGP signatures (this is all git is able to integrate with). After a less than desirable experience using GPG, without wrote bpb in Rust to replace GPG. I’ve been taking steps toward trying to sign and verify the data in the repo's index without shipping a copy of GPG with Rust to every user. This means I need to implement enough of the PGP protocol to create signatures and public keys that git will accept as valid. I’ve done this in a library which I’ve named pbp, this stands for Pretty Bad Protocol. This library implements parsing and generation for a small subset of the PGP protocol...

In the wake of Microsoft's acquisition of GitHub, the murmurs of replacing GitHub with something decentralized have been getting louder. In this article, Drew Devault points out that email-based git workflows are A Thing and one that works quite well. In particular, this blog post is a direct response to forge-net (formerly known as GitPub). They want to federate and decentralize git using ActivityPub, the same technology leveraged by Mastodon and PeerTube. But get this: git is already federated and decentralized! Drew has skin in the game via his sr.ht platform, and intends to make git send-email support a first-class citizen on it. Lots of interesting ideas at play here. After all these years is email still the web's killer app?

Imagine all your components organized on the cloud, made discoverable for your team and synced in all your projects. That’s Bit. This could be a game changer if they drill the management side of sharing your UI components. Intrigued? Watch the demo video to see what it's all about.

I hope this service doesn't promulgate the GitHub-profile-as-resumé meme, because it's definitely cool and fun to let it crunch the numbers and visualize what you've been up to all these years. For example, it determined that my most productive days are Mondays. I didn't know that!

After explaining why it all matters, Kushal Pandya covers four common situations that you might face while working with Git: I need to change the most recent commit I need to change a specific commit I need to add, remove, or combine commits My commit history doesn't make sense, I need a fresh start!

It can be used to perform SQL queries about the Git history and about the Universal AST of the code itself. gitbase is being built to work on top of any number of git repositories. The emphasis here is on querying a bunch of repositories at once, not digging deep in to the history of a single repo. It uses MySQL's wire protocol to communicate, so it can be accessed by any compatible client or library. gitbase is still in early alpha, but they're working hard to improve it quickly.

If this looks familar to you (demo here), that's because it's a community managed fork of Gogs. Why the fork? We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effort to build a more open and faster development model. This happened back in December of 2016, so it'd be interesting to compare and contrast the progress of both projects over time. At first glance, I'd say that Gogs is keeping up quite nicely with its BDFL model. But who knows, maybe the mere existence of Gitea spurred Unknwon on toward more actively maintaining Gogs.

This thing is packed with features, but the one that really impressed me (and may ultimately lead to me giving VS Code another go) is the Code Lens with inline git blames. Adds an unobtrusive, customizable, and themable, blame annotation at the end of the current line So cool! I do fear that it may become more annoying than useful over time, but you never know until you try.

Amjith shares a simple git alias he uses to resume work from where he left off. Perhaps you'll find it useful, too.

Ever since Heroku delivered git push-based deploys back in the day, the open source community has been hard at work creating alternative solutions with similar UX. Gitkube is the latest tool in this space, combining Docker and Kubernetes to get you started with your own git-based automation.

If you have a shared computer for "work" and "personal" AND you use Git (who doesn't), then this post will help you easily switch back and forth between the two. At work, most of the repositories are private, but at home most of my work is public, which means that my work email became public, and I didn’t like that. Hence, in this post I will share one way you can go about forgetting to switch back and forth and let the computer do it automatically for you.

We considered going this route with our new infrastructure, but I have to admit that I was ascared of having our secrets in public, even encrypted. My fears were most likely unfounded, and David Karapetyan does a great job of laying out the pros/cons in this article.