github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-08 20:58:16 -05:00
Code Issues 103 Packages Projects Releases 97 Wiki Activity

[GH-ISSUE #95] Mirror Repo with same name project name issue #180

New Issue
Closed
opened 2026-04-11 09:06:43 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-11 09:06:43 -05:00
Owner
Copy Link

Originally created by @svh1985 on GitHub (Sep 11, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/95

Originally assigned to: @arunavo4 on GitHub.

I have multiple starred Github repo's which have the same project name but with different owners:

  • user1/awesome-project (original)
  • user2/awesome-project (fork with changes)
  • user3/awesome-project (fork with changes)

When I import to Gitea only the first repo imported shows up as:

  • starred/awesome-project

Is it possible to add a suffix with the user account like so they show up in Gitea as:

  • starred/awesome-project-user1
  • starred/awesome-project-user2
  • starred/awesome-project-user3

Or maybe an org per user:

  • user1/awesome-project
  • user2/awesome-project
  • user3/awesome-project

Thanks!

Originally created by @svh1985 on GitHub (Sep 11, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/95 Originally assigned to: @arunavo4 on GitHub. I have multiple starred Github repo's which have the same project name but with different owners: - user1/awesome-project (original) - user2/awesome-project (fork with changes) - user3/awesome-project (fork with changes) When I import to Gitea only the first repo imported shows up as: - starred/awesome-project Is it possible to add a suffix with the user account like so they show up in Gitea as: - starred/awesome-project-user1 - starred/awesome-project-user2 - starred/awesome-project-user3 Or maybe an org per user: - user1/awesome-project - user2/awesome-project - user3/awesome-project Thanks!
GiteaMirror added the enhancement label 2026-04-11 09:06:43 -05:00
GiteaMirror commented 2026-04-11 09:06:45 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Sep 11, 2025):

@svh1985 Thanks for reporting this. Maybe we can make it configurable when conflicts like these happen.

<!-- gh-comment-id:3282314482 --> @arunavo4 commented on GitHub (Sep 11, 2025): @svh1985 Thanks for reporting this. Maybe we can make it configurable when conflicts like these happen.
GiteaMirror commented 2026-04-11 09:06:48 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Sep 14, 2025):

@svh1985 Please try v3.7.0 I have added one option in config. Let me know if this helps.

I have avoided adding org and also suffix together as that will cause migration headaches for existing users. Easiest was using prefix suffix so I have added that.

<!-- gh-comment-id:3289083678 --> @arunavo4 commented on GitHub (Sep 14, 2025): @svh1985 Please try v3.7.0 I have added one option in config. Let me know if this helps. I have avoided adding org and also suffix together as that will cause migration headaches for existing users. Easiest was using prefix suffix so I have added that.
GiteaMirror commented 2026-04-11 09:06:49 -05:00
Author
Owner
Copy Link

@svh1985 commented on GitHub (Sep 16, 2025):

@arunavo4 Thanks it works well!

Two suggestions:

  1. Would it not make more sense to put the setting on the Gitea side? As it seems more like a "Target" setting, and Gitea is the target.
  2. I think it would be great to also have the option (maybe a checkmark) to always apply the pre/suffix.
<!-- gh-comment-id:3298834751 --> @svh1985 commented on GitHub (Sep 16, 2025): @arunavo4 Thanks it works well! Two suggestions: 1. Would it not make more sense to put the setting on the Gitea side? As it seems more like a "Target" setting, and Gitea is the target. 2. I think it would be great to also have the option (maybe a checkmark) to always apply the pre/suffix.
GiteaMirror commented 2026-04-11 09:06:50 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Sep 16, 2025):

Sure will take the suggestions into consideration and make updates

<!-- gh-comment-id:3298862077 --> @arunavo4 commented on GitHub (Sep 16, 2025): Sure will take the suggestions into consideration and make updates
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#180
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?