GitHub for Writers: A Practical Guide to Branching and Pull Requests

This post is originally published on my site and is part of my work on documentation systems and Git workflows for writers. Sharing here for wider reach. In my previous post, I walked you through the fundamentals of GitHub for documentation. You learned how to clone a repository, make edits locally, and push changes directly to the main branch using GitHub Desktop. That workflow works beautifully when you're working solo or making quick fixes. But when you work as part of a documentation team, pushing directly to main becomes a liability. Imagine you're deep in a massive rewrite of the API guide (a 2-week project). It's currently a mess—half-written paragraphs, broken links, notes to yourself. Suddenly, a Product Manager rushes in: "The pricing page has a critical typo! It says $1000 instead of $10. We need to fix it NOW." You're stuck. You can't publish the pricing fix without also publishing your messy API rewrite. You have to back up your files, undo all your API work, fix the typo,