Fix an issue where changing an organization’s visibility caused problems when users had forked its repositories. (#37324)#37344
Merged
silverwind merged 1 commit intogo-gitea:release/v1.26from Apr 21, 2026
Conversation
…ems when users had forked its repositories. (go-gitea#37324) A quick fix go-gitea#37317 --- The current behavior for forks when an organization or repository is changed to private differs from GitHub. On GitHub, when a parent repository becomes private, the fork relationship is removed, which keeps the behavior simple and avoids visibility conflicts. I think we need a similar solution to handle cases where the parent repository becomes private while a fork remains public and the fork relationship is still preserved. --------- Signed-off-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>
GiteaBot
added
the
lgtm/need 2
silverwind
approved these changes
Apr 21, 2026
GiteaBot
added
lgtm/need 1
lunny
approved these changes
Apr 21, 2026
GiteaBot
added
lgtm/done
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
3 participants
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.
Backport #37324 by @lunny
A quick fix #37317
The current behavior for forks when an organization or repository is changed to private differs from GitHub.
On GitHub, when a parent repository becomes private, the fork relationship is removed, which keeps the behavior simple and avoids visibility conflicts.
I think we need a similar solution to handle cases where the parent repository becomes private while a fork remains public and the fork relationship is still preserved.