Category: GitHub

Pushed directly to a shared branch and something broke? Don’t rewrite history—revert it. This guide shows the safest ways to undo changes on GitHub without a PR: single commits, ranges, and merge commits, plus when (and when not) to use reset. We also cover using the GitHub “Revert” button, handling conflicts, and keeping an auditable trail via a quick PR.

Made a few local commits and realized they aren’t quite right—and nothing’s been pushed yet? This guide shows exactly how to unwind safely. Choose to discard everything, keep your changes unstaged, or keep them staged for a clean recommit, with copy-pasteable git reset commands for each path. We also cover peeling back the last N commits, aborting merges/rebases, and using git reflog as a safety net. Quick checks (git log, git status, git diff) help you verify before and after.

Most of the time, the safest way to undo a PR is to create a revert commit—no history rewrite, no surprises. This guide shows how to determine the merge method (merge, squash, or rebase), grab the right SHAs, and open a clean revert PR with GitHub CLI.

Need to keep staging (or a release branch) aligned with a single change from main without merging everything else? This guide walks through a minimal-diff workflow using GitHub CLI: branch from the base, restore only the target file(s) from the source ref, commit, and open a PR. It’s perfect for CI workflows and configs, keeps review tidy, and respects protected branches—so you get the change you want without the surprises you don’t.