Git Branches: Keep a Feature Reviewable
A branch that mixes refactoring and a new feature is hard to test and review. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Start from an up-to-date base, make one coherent change and commit with a clear message.
- Run relevant tests, review the diff and open a pull request with the behavior and risk described.
What to check
Rebase or merge with care when others share the branch; do not rewrite their published history casually. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.