Starred steals repos from also synced Organizations into starred Org #68

New Issue

GiteaMirror · 2025-10-31T15:30:21-05:00

GiteaMirror commented

2025-10-31 15:30:21 -05:00

Originally created by @OMGeeky on GitHub (Oct 27, 2025).

lets say we have this some repo called repo1 on the Organization Org1.
if we star this repo and then sync the starred repos to gitea it show up as expected as 'starred/repo1'.
That works fine, but if we added an Org1 to be synced I would expect repo1 to be under 'Org1/repo1' not starred. Also the overview on the organizations page show in my case 2 repositories, even though it should be 4 but since i have 2 of the repos also starred. Only the 2 i have not starred are counted i guess. When going to the repositories overview for that organization it shows all 4 (in gitea-mirror, but not gitea itself, since the repos are not part of the org) since both starred and Org1 are in the Organization column, so that part works.

I think it should prefer Organizations and only put it into the starred Org when the repo is either not inside an Org at all or if the Org it is in is not synced.
The way it currently is just looks wrong when looking at giteas repo site for an Org and just missing all the starred repos.

Great project btw :)

Originally created by @OMGeeky on GitHub (Oct 27, 2025). lets say we have this some repo called repo1 on the Organization Org1. if we star this repo and then sync the starred repos to gitea it show up as expected as 'starred/repo1'. That works fine, but if we added an Org1 to be synced I would expect repo1 to be under 'Org1/repo1' not starred. Also the overview on the organizations page show in my case 2 repositories, even though it should be 4 but since i have 2 of the repos also starred. Only the 2 i have not starred are counted i guess. When going to the repositories overview for that organization it shows all 4 (in gitea-mirror, but not gitea itself, since the repos are not part of the org) since both starred and Org1 are in the Organization column, so that part works. I think it should prefer Organizations and only put it into the starred Org when the repo is either not inside an Org at all or if the Org it is in is not synced. The way it currently is just looks wrong when looking at giteas repo site for an Org and just missing all the starred repos. Great project btw :)

GiteaMirror closed this issue

2025-10-31 15:30:21 -05:00

GiteaMirror commented

2025-10-31 15:30:22 -05:00

@OMGeeky commented on GitHub (Oct 27, 2025):

Alright, after trying some stuff I found that following these steps results in the configuration i expected:

deleting the starred/repo1 on gitea
head to organizations overview in gitea-mirror and try to mirror it again from there.
after these stept it created the repo under the Org1 instead of starred on gitea.

So the problem was probably that the starred repo was synced before adding the Org and that messed with it.

@OMGeeky commented on GitHub (Oct 27, 2025): Alright, after trying some stuff I found that following these steps results in the configuration i expected: 1. deleting the starred/repo1 on gitea 2. head to organizations overview in gitea-mirror and try to mirror it again from there. after these stept it created the repo under the Org1 instead of starred on gitea. So the problem was probably that the starred repo was synced before adding the Org and that messed with it.

GiteaMirror referenced this issue

2025-10-31 15:31:24 -05:00

[PR #70] [MERGED] Address Issue #68 and #69 #100

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#68