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
When adding a remote to a local repository (gin add-remote <remote_name> <location>) on gin and the location does not exist, the user can decide to create it directly. However, when using e.g. gin:<organization>/<repo> as remote, the repository is not created at the organization level, but under the user that is currently logged in.
I think there are 2 things to fix here:
The user should be informed if the remote can not be created at the organization level (i.e. due do lack of user rights)
If a repository can be created, than it should be at the specified organization and not under the user gin space.
The text was updated successfully, but these errors were encountered:
When adding a remote to a local repository (
gin add-remote <remote_name> <location>
) on gin and the location does not exist, the user can decide to create it directly. However, when using e.g.gin:<organization>/<repo>
as remote, the repository is not created at the organization level, but under the user that is currently logged in.I think there are 2 things to fix here:
The text was updated successfully, but these errors were encountered: