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.
Git hooks are a powerful feature that allows you to automate tasks during the lifecycle of a Git repository. Hooks are scripts that are triggered by specific Git events, such as making a commit or pushing code. They enable you to enforce coding standards, run tests, and other automated task
Git is a powerful version control system built on four core objects: commits, blobs, trees, and tags. These objects are fundamental to Git’s storage model, and understanding them provides valuable insights into how Git operates.
Let’s use a practical example to guide us through this process. By the end of this tutorial, you'll understand how to commit changes selectively, review modifications, and manage staged and unstaged changes.
You're likely to work with multiple branches for different features, bug fixes, and releases. While managing these branches, you might run into situations where you need to temporarily save your work without committing it, and later apply it on the same or even a different branch.
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.