-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
public=true #118
Comments
cdenneen
added a commit
to cdenneen/gitlab-mirrors
that referenced
this issue
Dec 14, 2018
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
cdenneen
added a commit
to cdenneen/gitlab-mirrors
that referenced
this issue
Feb 28, 2019
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)
Kiwi4Inovex
pushed a commit
to Kiwi4Inovex/gitlab-mirrors
that referenced
this issue
Feb 18, 2025
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)
Kiwi4Inovex
pushed a commit
to Kiwi4Inovex/gitlab-mirrors
that referenced
this issue
Mar 11, 2025
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)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#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: