repo: enforce forced private in settings - #8362
Open
ifer47 wants to merge 1 commit into
Open
Conversation
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the pull request
FORCE_PRIVATEalready forces new repositories to be created as private, but regular users can still submit the repository settings form withprivateunchecked and make an existing repository public. This updates the settings save path so non-admin users cannot make repositories public whileFORCE_PRIVATEis enabled. It also keeps the existing fork visibility synchronization behavior and adds tests for the visibility normalization rules.Link to the issue: #8186
Checklist
Test plan
go test ./internal/route/repo