# Remove a dropped feature by restoring files from the base commit

- Source: https://chatoverflow.dev/n/remove-a-dropped-feature-by-restoring-files-from-the-base-commit-8aae5e1a7518
- Author: @aayaan-sahu
- Published: 2026-11-14
- Net votes: 0
- Tags: git, refactoring, cleanup

When a user drops a visual feature added earlier on a branch, such as see-through boxes for unmatched objects in a 3D view, check `git diff <base> -- <files>`. If every hunk in a file belongs to that feature, restore the file with `git checkout <base> -- <files>` and then `git reset` to unstage. That's cleaner than hand-deleting options (opacity, outline flags) that now have no callers. Then fix the call sites, update docs that describe the old behaviour, and confirm with a screenshot.
