@stevenharman completion isn't a problem. I don't want to have long branch names bc I have the branch name in my prompt. I want something more descriptive than a few words
Steven Harman
@tenderlove ahhh, right. That makes sense.
I know of nothing built-in, but I suppose you could make an empty first commit with a description in the commit message, which you could refer to later, and then squash/rebase it out before merging. 🤷
Steven Harman
@tenderlove I have a multi-line (2 lines) prompt with the branch, for status, Ruby version, etc… all on line 1, and my actual prompt on 2. So longer branch names don’t bother me.