Adds an optional Target Organization field to the "Add Repository" dialog, allowing users to specify a destination Gitea org/user when adding a single repository
When left empty, the default mirror strategy is used (no behavior change)
The value is stored as the repo's destinationOrg override, same as editing it inline in the repository table
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/202
**Author:** [@arunavo4](https://github.com/arunavo4)
**Created:** 3/1/2026
**Status:** ✅ Merged
**Merged:** 3/1/2026
**Merged by:** [@arunavo4](https://github.com/arunavo4)
**Base:** `main` ← **Head:** `feat/add-repo-target-org`
---
### 📝 Commits (2)
- [`fe25a6c`](https://github.com/RayLabsHQ/gitea-mirror/commit/fe25a6c07cfd56cc896114eef6e67d3eb2730aad) feat: add target organization field to Add Repository dialog
- [`dc43f33`](https://github.com/RayLabsHQ/gitea-mirror/commit/dc43f332f89e9c99db172987313390ef09e2aad3) docs: add screenshot of target organization field in Add Repository dialog
### 📊 Changes
**5 files changed** (+37 additions, -3 deletions)
<details>
<summary>View changed files</summary>
➕ `docs/images/add-repo-target-org.png` (+0 -0)
📝 `src/components/repositories/AddRepositoryDialog.tsx` (+31 -1)
📝 `src/components/repositories/Repository.tsx` (+3 -0)
📝 `src/pages/api/sync/repository.ts` (+2 -2)
📝 `src/types/Repository.ts` (+1 -0)
</details>
### 📄 Description
## Summary
- Adds an optional **Target Organization** field to the "Add Repository" dialog, allowing users to specify a destination Gitea org/user when adding a single repository
- When left empty, the default mirror strategy is used (no behavior change)
- The value is stored as the repo's `destinationOrg` override, same as editing it inline in the repository table
Closes #200
## Screenshot

## Test plan
- [x] Build passes (`bun run build`)
- [x] All 248 tests pass (`bun test`)
- [ ] Add a repo without filling Target Organization → should use default strategy (same as before)
- [ ] Add a repo with Target Organization set → repo should show the custom org in the destination column
- [ ] Force-refresh an existing repo without Target Organization → existing `destinationOrg` should be preserved
- [ ] Force-refresh an existing repo with a new Target Organization → should update the destination
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/202
Author: @arunavo4
Created: 3/1/2026
Status: ✅ Merged
Merged: 3/1/2026
Merged by: @arunavo4
Base:
main← Head:feat/add-repo-target-org📝 Commits (2)
fe25a6cfeat: add target organization field to Add Repository dialogdc43f33docs: add screenshot of target organization field in Add Repository dialog📊 Changes
5 files changed (+37 additions, -3 deletions)
View changed files
➕
docs/images/add-repo-target-org.png(+0 -0)📝
src/components/repositories/AddRepositoryDialog.tsx(+31 -1)📝
src/components/repositories/Repository.tsx(+3 -0)📝
src/pages/api/sync/repository.ts(+2 -2)📝
src/types/Repository.ts(+1 -0)📄 Description
Summary
destinationOrgoverride, same as editing it inline in the repository tableCloses #200
Screenshot
Test plan
bun run build)bun test)destinationOrgshould be preserved🤖 Generated with Claude Code
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.