-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buggitGIT issuesGIT issuesgood first issueIssues identified as good for first-time contributorsIssues identified as good for first-time contributorshelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunitiesverifiedVerification succeededVerification succeeded
Milestone
Description
- VSCode Version: 1.30.1
- OS Version: Windows 10 - build 1803
Steps to Reproduce:
- Create new branch "git checkout -b @JA/feature1"
- VS Code display branch like below

- Click on publish icon, which spins and does nothing and produces this log.
git push -u origin refs/heads/@JA/feature1
To https://xxxxxxx.visualstudio.com/MyProject/_git/MyProject
- [new branch] @JA/feature1 -> @JA/feature1
git status -z -u
git symbolic-ref --short HEAD
git rev-parse --symbolic-full-name @JA/feature1
git rev-parse refs/heads/@JA/feature1
git rev-parse --symbolic-full-name refs/heads/@JA/feature1@{u}
fatal: no such branch: 'refs/heads/@JA/feature1'
git for-each-ref --format %(refname) %(objectname) --sort -committerdate
git remote --verbose
Issues:
- Publish works. I can see my branch on server repo but I also get above error. After publish icon remains same.

- Icon notifications stop working. I don't see any indication if there is any pending commit to push or pull latest changes.
I think it was working fine until 1.28 or 1.29
Note:
If I create branch with name like "feature1", everything works as expected.
Does this issue occur when all extensions are disabled?: Yes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buggitGIT issuesGIT issuesgood first issueIssues identified as good for first-time contributorsIssues identified as good for first-time contributorshelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunitiesverifiedVerification succeededVerification succeeded