-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plus sign in the feature branch name #148
Comments
Git supports the + so it is specific to gitflow:
|
Same issue. The "+" character doesn't work with gitflow. Thanks for your work ! |
See petervanderdoes/gitflow-avh#148 for a full description of this issue. In short, the export can fail (either raising an error from the shell, or silently exporting an incorrect value) if the path to the repo contains spaces. It is solved by quoting the value to be exported, preventing the shell from splitting the result into multiple values (and then trying to parse those as multiple variable-names & values). Fixes nvie#148
Just stepped on the trap as well... Hopefully we can have this fixed soon, plus sign is a valid way to add build info to version number per semver spec. |
👍 |
the following patch fixed things for me: --- /usr/local/Cellar/git-flow/0.4.1/libexec/bin/gitflow-common.orig 2017-10-05 20:35:16.000000000 -0500
+++ /usr/local/Cellar/git-flow/0.4.1/libexec/bin/gitflow-common 2017-10-05 20:35:03.000000000 -0500
@@ -50,7 +50,15 @@ escape() {
# set logic
has() {
- echo " $@ " | grep -q " $(escape $item) "
+ local item=$1; shift
+ for s in $@; do
+ if [ "$item" = "$s" ]; then
+ return 0
+ fi
+ done
+ return 1
+ # the following code has issues with + in the branch names
+ #echo " $@ " | grep -q " $(escape $item) "
}
# basic math |
I had a feature branch named 'feature/google+' and unfortunately none of the git flow command could find it. I got all the time:
Branch 'feature/google+' does not exist and is required.
Problably some problem with grep or sth. Would be worthy to check also some other characters which are allowed in branch names but are not caught by git flow
Regards
Michal
The text was updated successfully, but these errors were encountered: