adam/gitea-mirror
1
0 Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-11-03 07:42:19 +01:00
Code Issues 4 Packages Projects Releases Wiki Activity

Config: Name Collision Strategy dropdown does not persist (no save button) #135

New Issue
Closed
opened 2026-10-05 01:43:43 +02:00 by adam · 4 comments
adam commented 2026-10-05 01:43:43 +02:00
Owner
Copy link
Copy source

Description

The Name Collision Strategy setting in Configuration → Connections → GitHub Configuration defaults to repo-owner. Changing it to owner-repo does not persist; navigating away and returning shows it reverted to repo-owner. There is no explicit Save button for this setting.

Other settings on the same page auto-save correctly; only this drop-down is affected.

Impact: Repos are being created with the repo-owner naming pattern even after attempting to change the setting — confirming the change is not being persisted at all, not just a UI display issue.

Under the hood

Field appears to map to starredDuplicateStrategy in the configs table (schema: "suffix" | "prefix" | "owner-org", default "suffix"). Guessing that the onChange handler either doesn't fire or the save call silently fails.

Additionally, the docs don't list an environment variable for this field, so I was unable to test or workaround the issue by setting via the compose file.

Environment

  • Gitea-Mirror Version: v3.19.1
  • Install: Fresh Docker install
  • Browser: Firefox

Steps to Reproduce

  1. Configuration → Connections → GitHub Configuration
  2. Change Name Collision Strategy from repo-owner to owner-repo
  3. Navigate to another settings page
  4. Return to GitHub Configuration
  5. Name Collision Strategy is back to repo-owner

Expected

Selection persists after change (auto-save like other dropdowns) or a Save button is present for the setting.

### Description The `Name Collision Strategy` setting in Configuration → Connections → GitHub Configuration defaults to `repo-owner`. Changing it to `owner-repo` does not persist; navigating away and returning shows it reverted to `repo-owner`. There is no explicit Save button for this setting. Other settings on the same page auto-save correctly; only this drop-down is affected. Impact: Repos are being created with the repo-owner naming pattern even after attempting to change the setting — confirming the change is not being persisted at all, not just a UI display issue. ### Under the hood Field appears to map to starredDuplicateStrategy in the configs table (schema: "suffix" | "prefix" | "owner-org", default "suffix"). Guessing that the onChange handler either doesn't fire or the save call silently fails. Additionally, the docs don't list an environment variable for this field, so I was unable to test or workaround the issue by setting via the compose file. ### Environment - Gitea-Mirror Version: v3.19.1 - Install: Fresh Docker install - Browser: Firefox ### Steps to Reproduce 1. Configuration → Connections → GitHub Configuration 2. Change `Name Collision Strategy` from `repo-owner` to `owner-repo` 3. Navigate to another settings page 4. Return to GitHub Configuration 5. `Name Collision Strategy` is back to `repo-owner` ### Expected Selection persists after change (auto-save like other dropdowns) or a Save button is present for the setting. <!-- github-sync-id:4683929960 -->
adam closed this issue 2026-10-05 01:43:43 +02:00
adam commented 2026-10-05 01:43:44 +02:00
Author
Owner
Copy link
Copy source

@agent00bob can you give it a try again with the latest verison. Should be fixed now

@agent00bob can you give it a try again with the latest verison. Should be fixed now <!-- github-comment-id:4748240879 -->
adam commented 2026-10-05 01:43:44 +02:00
Author
Owner
Copy link
Copy source

@agent00bob can you give it a try again with the latest verison. Should be fixed now

@arunavo4 just pulled and tested. Looks to be persisting now. I haven't tried mirroring another repo yet. I renamed the repos manually in Forgejo thinking the sync/mirrors would persist based on the github address, not the repo name. But it looks like it broke them. I'm not sure if that's an issue or just working as designed. So not sure how to test on my sync'd/mirrored repos without removing them and readding.

> [@agent00bob](https://github.com/agent00bob) can you give it a try again with the latest verison. Should be fixed now @arunavo4 just pulled and tested. Looks to be persisting now. I haven't tried mirroring another repo yet. I renamed the repos manually in Forgejo thinking the sync/mirrors would persist based on the github address, not the repo name. But it looks like it broke them. I'm not sure if that's an issue or just working as designed. So not sure how to test on my sync'd/mirrored repos without removing them and readding. <!-- github-comment-id:4754340573 -->
adam commented 2026-10-05 01:43:45 +02:00
Author
Owner
Copy link
Copy source

@agent00bob can you maybe give it a try on a fresh sync

@agent00bob can you maybe give it a try on a fresh sync <!-- github-comment-id:4754349200 -->
adam commented 2026-10-05 01:43:46 +02:00
Author
Owner
Copy link
Copy source

@arunavo4 okay, looks like it worked. Thanks very much for the quick turn!

@arunavo4 okay, looks like it worked. Thanks very much for the quick turn! <!-- github-comment-id:4754424159 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/gitea-mirror#135