Closed danielpunkass closed 2 years ago
Please read the comment block starting the function your are modifying. It both contains an explanation for why your patch is the wrong solution and what the right solution to the problem which triggered your PR is. Besides that, /
is perfectly valid in Git branch names, so there is no reason to sanitize it. Read the first item in the "Frequent Problems" section of the README for a crash course on Git branch naming.
Oh! I'm embarrassed to have glossed right over that comment in the sources. Thanks for explaining so patiently.
:)
"live and learn"
See Issue #32, I believe this is the correct fix for the underlying issue causing that import failure, or at least it addresses one of the possible branch naming problems that could lead to the issue.