-
Notifications
You must be signed in to change notification settings - Fork 755
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
Set visibility directly #2410
base: main
Are you sure you want to change the base?
Set visibility directly #2410
Conversation
Previously, when creating a repository from a template, it sets the visibility to either `Public` or `Private` and then edits the repo settings later to ensure the visibility is correct. Now it sets the `Visibility` parameter instead.
I'm seeing failing integration tests as a result of these changes:
Can you reproduce these? |
@littlelionking do you have an issue documenting what is wrong with the current approach? Switching to the GraphQL client has a number of downsides and I can't see what it actually achieves here? |
925 was referenced in my PR from feb.
Yeah, I would prefer if there was a rest api option.
Maybe I set something up wrong when I ran the tests. I'm not looking to use |
#2151 but I won't delete my fork