Git is one of the most popular and widely used version control systems today. Whether you’re a developer or DevOps engineer, Git is an essential tool for managing code, collaboration, and automation workflows. This guide will walk you through the process of installing Git on different operating systems: Windows, macOS, and Linux.
In the previous post, we discussed how to use git stash to temporarily save changes without committing them. Now, we'll dive deeper into how to apply and clear stashes when you're ready to bring your changes back or clean up your stash history.
When you need to quickly switch branches, but you have uncommitted changes in your working directory. Committing these unfinished changes might not be desirable, and discarding them would result in a loss of your work. This is where Git’s stash command comes into play.
Rebasing is a common technique to keep a clean and linear history. However, one of the challenges developers face while performing a rebase is dealing with merge conflicts. During a rebase, conflicts may arise if the changes in your branch overlap or contradict the changes in the branch
I packaged my small Bash module, cleaned the code, added structure, and finally published it on GitHub. In this post, I walk through preparing a project for public release, choosing a layout, documenting it properly, and getting it ready for future automation.
A friendly, no-panic walkthrough for building a CI pipeline that tests your code, tags it, packages it, and ships a GitHub Release all by itself. You write code, GitHub does the rest. Towels optional.
A hands-on story about discovering a bug in my Bash module, opening an issue on GitHub, assigning it to myself, creating a branch, fixing the code, adding tests, and closing the issue—step by step, with screenshots and code along the way.
Rebasing in Git is a powerful tool to keep your commit history clean and organized, but it comes with some challenges. When done correctly, a rebase creates a linear and clean history, but mistakes can lead to a confusing history or even conflicts.
A practical, step-by-step guide to installing the GitHub CLI (gh) on Windows, macOS, Linux, WSL, and even inside Docker. Covers package managers, manual installs, authentication, upgrades, and common troubleshooting tips.
A new feature joins my Bash module: a stopwatch that measures how long each shell command takes. In this post I walk through the whole process—planning, branching, coding, testing, updating the installer, and preparing a pull request—all with a healthy dose of fun.
Learn how to file a clear, useful GitHub issue—without summoning chaos into your repo. In this guide, I walk through reporting a real bug in my own Bash module and show exactly how to write the kind of issue maintainers actually enjoy reading.
Both git merge and git rebase are methods used to integrate changes from one branch into another. Although both achieve the goal of integrating changes, they do so in entirely different ways. Understanding the difference between them is crucial for effectively managing your Git history
Git is the most popular version control system, and one reason for its efficiency is how it stores data. Unlike traditional version control systems, which track changes in files, Git stores snapshots of the entire project’s file structure. In this post, we'll explore Git's inner workings.