delivery-work does not read multi slash branch names
#255
Labels
Comments
extsoft
added a commit
that referenced
this issue
Apr 15, 2020
`git elegant deliver-work` incorrectly reads the name of the upstream branch if it contains at least one slash like `feature/123`. This is because the used pattern matching logic doesn't expect remote branch names like `origin/feature/123`. In order to solve it, the new `transformation` plugin is introduced. It provides functions that parse remote branch names correctly. Now, the plugin handles branch translation (mapping) for `deliver-work` command as well as for `accept-work` and `obtain-work` in order to prevent possible errors in the future. #255
4 tasks
extsoft
added a commit
that referenced
this issue
Apr 15, 2020
`git elegant deliver-work` incorrectly reads the name of the upstream branch if it contains at least one slash like `feature/123`. This is because the used pattern matching logic doesn't expect remote branch names like `origin/feature/123`. In order to solve it, the new `transformation` plugin is introduced. It provides functions that parse remote branch names correctly. Now, the plugin handles branch translation (mapping) for `deliver-work` command as well as for `accept-work` and `obtain-work` in order to prevent possible errors in the future. #255
|
Fixed since 0.18.1 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bug
git elegant deliver-workincorrectly reads the name of the upstream branch if it contains at least one slash likefeature/123.Steps to reproduce
git checkout -b feature/123git elegant deliver-work# first pushgit elegant deliver-work# next pushExpected behavior
The third command should update
feature/123branch inorigin. Now, it pushes a new branch called123(so,feature/is removed).My environment
git --version: 2.26.0bash --version: 3.2.57The text was updated successfully, but these errors were encountered: