Source Control, Branching, and Pull Request
A focused chapter on source control, branching, and pull request, with practical delivery concerns, trade-offs, and the operational questions behind CI/CD work.
Why Your Code Needs a Shared Home Before You Even Think About CI/CD
You are working on an application by yourself. All the code lives on your laptop. You can change anything, anytime, and you never worry about breaking
How Branching Helps Teams Work on Code Without Stepping on Each Other
Imagine two developers opening the same file at the same time. One is adding a new feature. The other is fixing a bug in the same function. They both
Why Pull Requests Matter More Than Code Review
You have been working on a feature for two days. The code compiles, the tests pass on your machine, and you are confident it works. You push your branch
Merge, Tag, and Release: Keeping Track of What Goes to Production
You just finished reviewing a pull request. The code looks good, the tests pass, and your teammate approved the changes. Now what?
How to Choose a Branching Strategy That Actually Fits Your Team
You have two developers working on the same application. One is adding a new feature, the other is fixing a bug. They both start from the same codebase
The Paper Trail That Saves Your Production Debugging
A production bug appears. Data is wrong. Users are complaining. The on-call developer opens the commit log and sees message after message that says "fix