For a long time this site hasn’t had comments. When I moved from WordPress to a static site generator, the old commenting system didn’t come along for the ride. The result was simple pages, fast builds, and a very quiet comment box that no longer existed.
I’ve gone back and forth on whether to bring comments back. Most days I enjoy the focus of writing and publishing without worrying about moderation. Other days I miss the conversations that used to happen underneath posts. I’ve had emails and DMs that would have been even more useful as public threads, where other readers could add context or correct me when I get something wrong.
As developers, we often find ourselves forking open-source projects on GitHub to contribute or to modify for our specific needs. While creating a fork is a simple process, keeping it up-to-date with the original repository can sometimes be confusing. In this blog post, we will explore the steps required to keep your GitHub fork updated with the latest changes from the upstream repository.
Step 1: Configure the Upstream Repository To keep your fork updated, you must first configure the upstream repository – the original project from which you created your fork. This ensures you can easily fetch the latest changes from the upstream repository.