Every now and then my inbox in Github shows x total unread updates without having actual updates. When I click on it, there are no unread notifications. This is a known issue and it’s been around for a while. The notifications are called “ghost notifications” and they are not visible in the UI.

If you are like me you probably typed more than once git stash and meant git stash list while working on many different things at the same time. If not, then feel free to go somewhere else and don’t waste your time here :]

GoHugo’s documentation recently started to show functions and methods with their “real” name, instead of the alias used in the GoHugo codebase. Did you for instance knew that apply is actually collections.Apply and append is collections.Append? Knowing these exact names seems to be important to me, because I think it’s easier to understand what functions are connected and what features are available.

In my projects, I often encounter situations where I need to update the version number of the project before making a release. I follow the Semantic Versioning (Semver) standard for versioning. In this blog post, I’ll demonstrate how to retrieve the next Semver version number using a Bash script.

Despite its many advantages and nifty features of Git, there’s one feature it lacks: a status hook. In Git, hooks are scripts that I can execute automatically at specific points during the version control process. These hooks perform custom actions, such as running tests, enforcing coding standards, or sending notifications, at various stages like pre-commit, post-commit, and post-merge.

Hugo in version 0.114.0 finally introduced the changes I wrote about a while back. The hugo command on the CLI now dropped the –log and –verboseLog flags and deprecated the –verbose and –debug flags. Instead, it now uses the –logLevel as an indicator of verbosity.

For some time now, I was receiving the following warnings after an otherwise successful run of apt update: plain COPY 1W: http://linux.dropbox.com/ubuntu/dists/disco/Release.gpg: 2Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), 3see the DEPRECATION section in apt-key(8) for details. 4W: http://prerelease.keybase.io/deb/dists/stable/InRelease: 5Key is stored in legacy trusted.

Hugo, the little static site generator that powers this website, offers two main content organization options known as page bundles. Page bundles provide a way to group page resources in leaf and branch bundles, allowing for more structured content management. In this quick guide, I will show you how to easily switch between the two types without much manual work.

There is a recent commit in GoHugo’s repository that removes several CLI parameters I was using in my projects. Those flags were –debug, –log, –logFile and –verboseLog. While I am not discussing this decision (I don’t like it, but I understand that keeping these things in the software needs someone able to keep them up to date and conclusive and the developer of the software seems to be unable to) I am still interested in the idea of having a file with all output of my Hugo runs available so I can parse through it and see what is going on while building the site.