This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Git tries wrong branch when branch is named beginning with + #1824
Open

Description
@TwoHorus commented on Dec 5, 2018, 2:32 PM UTC:
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
Cannot push in atom, whilst cli pushing works. I suppose the Branch name starting with a Plus symbol is not parsed correctly.
Steps to Reproduce
- Create Branch in gitlab
- name it +Pages
- switch branches in atom and push to the branch
Expected behavior: Atom Pushes to Branch
Actual behavior: Atom throws: error: src refspec Pages does not match any.
error: failed to push some refs to
'https://git.organisation.com/user/project
Reproduces how often: Every time
Version 1.33.0
Additional Information:
CMD ALT I reveals
Uncaught (in promise) GitError: git push origin +Pages in /Users/Admin/Documents/GitHub/project exited with code 1
stdout:
stderr: error: src refspec Pages does not match any.
error: failed to push some refs to 'https://git.company.org/user/project.git'
at new GitError (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2766914)
at Promise (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2771732)
at <anonymous>
This issue was moved by rsese from atom/atom#18544.