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
Minor issue because it only happens when you try to do an aunty release when in a project that is not connected to a remote origin, but maybe we should return a better error like "you need to be connected to a remote origin to deploy" (or else allow releases without a git repo attached???), and also update the default name const here to main anyway:
Minor issue because it only happens when you try to do an
aunty release
when in a project that is not connected to a remote origin, but maybe we should return a better error like "you need to be connected to a remote origin to deploy" (or else allow releases without a git repo attached???), and also update the default name const here tomain
anyway:aunty/src/utils/git.js
Line 20 in eeef0eb
Once I added the remote git repo on GitHub I could do a release.
The text was updated successfully, but these errors were encountered: