Issue when creating a merge request with nested branch name

[Tomas Lima]

Hi

I just updated from version 4.2.5 to both 4.2.6 and 4.2.7 and I'm seeing this bug:
When I create a merge request from a branch with nested names (say `tomas/branch-name`), SourceTree pushes correctly but opens a new browser tab with an incorrect URL:

https://gitlab.com/my-repo/my-repo/-/merge_requests/new?merge_request%5Bsource_branch%5D=tomas%252Fbranch-name

Pay attention to the end: `source_branch%5D=tomas%252Fbranch-name`

If I manually replace in the URL `%252F` with `%2F` and hit enter, it opens the correct URL.

For now, I downgraded to version 4.2.5 to keep this functionality unbroken.

Thank you 

[Matt Stone]

I couldn't find an open issue on the public Jira board for Sourcetree (apart from an old identical issue from v2.5.1) so have created a new issue here: https://jira.atlassian.com/browse/SRCTREE-8179

If you've also had this issue please Add your Vote to the issue above so help increase it's visibility with the hope it gets triaged and fixed soon.

[kvlsrg]

Same issue in 4.2.9 (using GitLab Enterprise).

Slashes in branch name double escaped for sure ("%252F" instead of "%2F").

[Jinling Wang]

Same issue with 4.2.8

[Matt Stone]

Still an issue in 4.2.8

[Matt Stone]

I'm also getting this issue on both 4.2.6 and 4.2.7, it looks like the slash in the branch name is getting double-encoded.

For reference I'm getting this issue both on Github and Gitlab so looks to be a Sourcetree bug that is not yet fixed