[GH-ISSUE #23] Bug: Unexpected behavior with "Preserve Org Structure" and starred repositories #12

New issue

Closed

opened 2026-02-27 15:54:31 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:54:31 +03:00

Owner

Originally created by @neo-pan on GitHub (Jun 6, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/23

Hi, thanks for your clarification in #22.

However, I’m observing behavior that seems inconsistent with your explanation. Here’s what’s happening on my side when "Preserve Org Structure" is enabled:

For starred repositories without an organization on GitHub, they are being mirrored into my Gitea username namespace.
For starred repositories that belong to a GitHub organization, a new organization is created on Gitea, and the repository is mirrored there.

This seems to contradict the expected behavior that starred repositories should follow the "Starred Repositories Organization" setting regardless of the "Preserve Org Structure" toggle.

Could you please confirm whether this is a bug?

By the way, I'm using gitea-mirror v2.12.0. Let me know if you need further logs or config info!

Thanks again for the great project.

Originally created by @neo-pan on GitHub (Jun 6, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/23 Hi, thanks for your clarification in [#22](https://github.com/arunavo4/gitea-mirror/issues/22#issuecomment-2945521022). However, I’m observing behavior that seems inconsistent with your explanation. Here’s what’s happening on my side when "Preserve Org Structure" is enabled: - For starred repositories without an organization on GitHub, they are being mirrored into my Gitea username namespace. - For starred repositories that belong to a GitHub organization, a new organization is created on Gitea, and the repository is mirrored there. This seems to contradict the expected behavior that starred repositories should follow the "Starred Repositories Organization" setting regardless of the "Preserve Org Structure" toggle. Could you please confirm whether this is a bug? ![Image](https://github.com/user-attachments/assets/3adad833-f165-4e39-87a0-2074244a9694) ![Image](https://github.com/user-attachments/assets/fd043f99-0b4d-49a7-b4fb-6e281f94a09b) ![Image](https://github.com/user-attachments/assets/d321b2cf-1be3-4c1d-ac48-b8b0f1e9b368) By the way, I'm using gitea-mirror v2.12.0. Let me know if you need further logs or config info! Thanks again for the great project.

kerem closed this issue

2026-02-27 15:54:32 +03:00

kerem commented

2026-02-27 15:54:32 +03:00

Author

Owner

@arunavo4 commented on GitHub (Jun 15, 2025):

Hi @neo-pan, its been a busy week for me. But I have looked into the UX of this confusion and I have made a lot of updates to the configuration page in a quest to simplify the confusion. I will be testing it this week. Feel free to test out the latest verison and report bugs here if you find any,

@arunavo4 commented on GitHub (Jun 15, 2025): Hi @neo-pan, its been a busy week for me. But I have looked into the UX of this confusion and I have made a lot of updates to the configuration page in a quest to simplify the confusion. I will be testing it this week. Feel free to test out the latest verison and report bugs here if you find any,

kerem commented

2026-02-27 15:54:32 +03:00

Author

Owner

@arunavo4 commented on GitHub (Jun 17, 2025):

@neo-pan closing this as I have fixed this issue in the latest release v2.16.2

@arunavo4 commented on GitHub (Jun 17, 2025): @neo-pan closing this as I have fixed this issue in the latest release `v2.16.2`

kerem referenced this issue

2026-02-27 15:55:08 +03:00

[PR #13] [MERGED] Fix Bun permissions issue in LXC container installer #100