Readable branch names age well
Use a stable category, an optional issue key, and a short task phrase. Lowercase ASCII names work reliably across shells and hosting platforms. Keep the meaning clear enough that teammates can identify the work in a branch list.
Examples
feature/dev-142-add-ssh-url-conversion
fix/handle-empty-diff
docs/reset-vs-revert-warningAfter creating it, switch with git switch -c <branch-name>. See the Git branching cheat sheet.