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
The original `true` or `false` setting for public used to set to repository visibility to private or public.
This does exactly the same thing keeping the `public=false/true` configuration setting.
Removing `public` configuration in favor of full `visibility` support (public, private, internal) will require additional work so for now this is a stop gap for samrocketman#118
The original `true` or `false` setting for public used to set to repository visibility to private or public.
This does exactly the same thing keeping the `public=false/true` configuration setting.
Removing `public` configuration in favor of full `visibility` support (public, private, internal) will require additional work so for now this is a stop gap for samrocketman#118
(cherry picked from commit 3ff356a)
#90 has reared it's head again.
Please take a look but new projects are being created as Private even with
public=true
being set.Confirmed with checking out 0.6.1 this is still the setting in config.sh.SAMPLE
The text was updated successfully, but these errors were encountered: