There is a bug when you "Create a new remote..." and give it a name with a forward-slash:
Of course, I then pull the remote afterwards (no problems).
Then I make some changes and commit them.
Then I perform my first push:
As you can see, the very first push was successful.
I make some more changes, and commit them.
I attempt my second push:
When I hover the cursor over "Push to current tracking branch", I am not permitted to select it. Additionally, "Push to another branch" (which is pre-selected) has an empty, unpopulated drop-down list. I click on the "Refresh" icon, it performs a fetch request, and then the list remains empty.
Of course, with no other branch to push to, I can't push anything at all!
The bug
It turns out that because I named my remote with a forward slash between the words "GitHub" and "MyUniqueProject", the Brackets-Git extension is unable to perform further push requests.
Although we can push the project the first time, we are unable to push the project a second time due to this forward slash.
Workaround
When creating remotes, don't use a forward slash in the name
Potential Solutions
When creating a new remote, ensure text validator checks for forward slashes in the remote name
Squash the bug, and allow users to use a forward slash in their remote names
There is a bug when you "Create a new remote..." and give it a name with a forward-slash:
As you can see, the very first push was successful.
When I hover the cursor over "Push to current tracking branch", I am not permitted to select it. Additionally, "Push to another branch" (which is pre-selected) has an empty, unpopulated drop-down list. I click on the "Refresh" icon, it performs a fetch request, and then the list remains empty.
Of course, with no other branch to push to, I can't push anything at all!
The bug
It turns out that because I named my remote with a forward slash between the words "GitHub" and "MyUniqueProject", the Brackets-Git extension is unable to perform further push requests.
Although we can push the project the first time, we are unable to push the project a second time due to this forward slash.
Workaround
When creating remotes, don't use a forward slash in the name
Potential Solutions
Sidenote
This is the root cause for Issue#1047