Describe the feature or problem you’d like to solve
Using some branch naming conventions when a 3rd party issue tracker like Jira ticket number is expected in branch name worked until recently prediction mechanism started replacing dashes as well which makes the use of gh CLI slower than using --web. Dunno actually what really changed but so far it worked like that.
Removing dashes isn't humanizing the title, it's breaking functionality that lots of automated tooling I've used relies on. At the very least, it could verify with it's something like - before blanket removing it. Automatically removing dashes just means I have to go manually add them back in which is what this functionality is supposed to prevent--making me modify the title myself.
Proposed solution
In
remove dash
"-" from replacing chars list.
Additional context
For eg. a branch called PRJ-123_Fixes_pack4 should be humanized as PRJ-123 Fixes pack4 instead of PRJ 123 Fixes pack4 which breaks my CI.
Describe the feature or problem you’d like to solve
Using some branch naming conventions when a 3rd party issue tracker like Jira ticket number is expected in branch name worked until recently prediction mechanism started replacing dashes as well which makes the use of
ghCLI slower than using--web. Dunno actually what really changed but so far it worked like that.Removing dashes isn't humanizing the title, it's breaking functionality that lots of automated tooling I've used relies on. At the very least, it could verify with it's something like - before blanket removing it. Automatically removing dashes just means I have to go manually add them back in which is what this functionality is supposed to prevent--making me modify the title myself.
Proposed solution
In
cli/utils/utils.go
Line 59 in 6cc7712
"-"from replacing chars list.Additional context
For eg. a branch called
PRJ-123_Fixes_pack4should be humanized asPRJ-123 Fixes pack4instead ofPRJ 123 Fixes pack4which breaks my CI.