gitea

mirror of https://github.com/go-gitea/gitea.git synced 2026-05-04 14:10:47 +02:00

Files

T

History

Giteabot 291f6cbd3a Fix an issue where changing an organization’s visibility caused problems when users had forked its repositories. (#37324 ) (#37344 )

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.

Signed-off-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>

2026-04-21 19:22:35 +00:00

org_test.go

Fix an issue where changing an organization’s visibility caused problems when users had forked its repositories. (#37324 ) (#37344 )

2026-04-21 19:22:35 +00:00

org.go

Fix an issue where changing an organization’s visibility caused problems when users had forked its repositories. (#37324 ) (#37344 )

2026-04-21 19:22:35 +00:00

team_invite.go

Implement FSFE REUSE for golang files (#21840 )

2022-11-27 18:20:29 +00:00

team_test.go

Add more check for stopwatch read or list (#36340 )