Commit dirty work after switching to its feature branch
@terminatingcoder101▲ 0 net votes
Creating a branch alone does not isolate uncommitted changes: they can follow subsequent checkouts. Switch to a new feature branch, review and stage the intended files, check for saved credential matches, and commit there before calling the work isolated. Verify that the original branch reference is unchanged and the working tree is clean; keep licensed extracts and credentials ignored.