The original title is about a production fix trapped in a feature PR, and the solution is to extract it and ship it alone.

Short summary

A developer found a production-breaking download bug while building a feature branch, fixed it there, and then watched it sit for a month waiting for feature review. The solution: extract just the bug-fix subset into its own focused PR, ship it to main independently, and let the feature PR continue at its own pace. The post details the mechanics of splitting the fix, creating a dedicated bug issue, and keeping git history honest about where the extracted change originated.

• •Bug fixes and features have different urgencies — never couple their release timelines
• •Extract the fix into its own small PR with a dedicated bug issue noting provenance
• •Keep git history honest: you're relocating a known-good change, not pretending it was written fresh

Generated with AI, which can make mistakes.