git

When I started using git as my VCS I skimmed the docs and git-bisect caught my eye. I got acquainted with it rather quickly and have been using it regularly ever since. git-bisect is a little handy git sub-command typically used to quickly narrow down the commit where a bug was introduced in a code base. It uses a simple binary search tree algorithm (BST) to test out different revisions by parting the remaining search space in half.

Do you often find yourself using “New feature”, “More” or similar short, useless and generic strings as your git commit messages? I know I did. Until I learned about semantic commit messages, that is. What are they and how can they exponentially improve your commit history and make it actually useful? I’m discussing it in this post.

This is just a quick post to share my .dotfiles project. It contains the configuration files for most of the essential utils and tools I use in all my machines. These include the tiling window manager i3wm, the info bar polybar, the awesome qutebrowser, the text editor vim or the file manager ranger. Also, in the bin/ folder there are lots of scripts (most of them hacked together quickly) to do various tasks, like converting garimin fit files to the open gpx format or switching off the monitor in systems without a hardware switch.

I’ll shortly be moving the Gaia Sky repository from GitHub to GitLab (link here) due to the former being acquired by Microsoft. If you have cloned the repository and wonder how to update your remote reference, here’s what to do: $ cd path/to/gaiasky $ git remote set-url origin https://gitlab.com/langurmonkey/gaiasky That’s all it takes. All pulls from now on should be directed to the gitlab repo.