You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you create a new repo and undo the initial commit the Publish button in the main menu is disabled by design, however, you can still access the publish the repo via the Repo Settings modal, which results in an "unborn branch" error.
v0.6.1, OSX 10.11.5
Reproduce:
Create new repo (File > New Repo)
Undo initial commit (Publish button should disable)
Go to Repository > Repo settings
Click Publish, try to publish
The Publish button on the repo settings modal should be disabled and/or the text should change to reflect the state.
The text was updated successfully, but these errors were encountered:
joshaber
changed the title
Disable Publish button if no commits for a new repo
Disable Publish button in Repository Settings if no commits for a new repo
Jun 22, 2017
If you create a new repo and undo the initial commit the Publish button in the main menu is disabled by design, however, you can still access the publish the repo via the Repo Settings modal, which results in an "unborn branch" error.
This makes me think we're going about it the wrong way - we should let the user publish always, and detect when the repository is unborn and skip the attempt to push the branch. There may need to be some UX thoughts about this to distinguish between publish and push, but maybe we just need to make "push" clear that it has nothing to push.
If you create a new repo and undo the initial commit the
Publish
button in the main menu is disabled by design, however, you can still access the publish the repo via the Repo Settings modal, which results in an "unborn branch" error.v0.6.1, OSX 10.11.5
Reproduce:
Publish
button should disable)Publish
, try to publishThe
Publish
button on the repo settings modal should be disabled and/or the text should change to reflect the state.The text was updated successfully, but these errors were encountered: