From 63308fc17068e81121eb11e747e7b8153c865257 Mon Sep 17 00:00:00 2001
From: aitbc <aitbc-agent@keisanki.net>
Date: Mon, 30 Mar 2026 17:26:11 +0200
Subject: [PATCH] fix: update repository URLs from private Gitea to public
 GitHub
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Repository URL Update - Complete:
✅ REPOSITORY URLS UPDATED: Changed from private Gitea to public GitHub
- setup.sh: Updated clone URLs to use github.com/aitbc/aitbc
- docs/infrastructure/README.md: Updated manual setup instructions
- Reason: Gitea is private development-only, GitHub is public repository

✅ SETUP SCRIPT UPDATED:
🔧 Primary URL: https://github.com/aitbc/aitbc.git (public)
🔧 Fallback URL: git@github.com:aitbc/aitbc.git (SSH)
📁 Location: /opt/aitbc/setup.sh (clone_repo function)
🎯 Purpose: Public accessibility for all users

✅ DOCUMENTATION UPDATED:
📚 Infrastructure README: Updated manual setup instructions
📝 Before: sudo git clone https://gitea.bubuit.net/oib/aitbc.git /opt/aitbc
📝 After: sudo git clone https://github.com/aitbc/aitbc.git /opt/aitbc
🎯 Impact: Public accessibility for documentation

✅ PRESERVED DEVELOPMENT REFERENCES:
📊 scripts/monitoring/monitor-prs.py: Gitea API for development monitoring
📊 scripts/testing/qa-cycle.py: Gitea API for QA cycle
📊 scripts/utils/claim-task.py: Gitea API for task management
🎯 Context: These are internal development tools, should remain private

✅ URL CHANGE RATIONALE:
🌐 Public Access: GitHub repository is publicly accessible
🔒 Private Development: Gitea remains for internal development tools
📦 Setup Distribution: Public setup should use public repository
🎯 User Experience: Anyone can clone from GitHub without authentication

✅ IMPROVED USER EXPERIENCE:
✅ Public Accessibility: No authentication required for cloning
✅ Reliable Source: GitHub is more reliable for public access
✅ Clear Documentation: Updated instructions match actual URLs
✅ Development Separation: Private tools still use private Gitea

RESULT: Successfully updated repository URLs from private Gitea to public GitHub for public-facing setup and documentation while preserving internal development tool references to private Gitea.
---
 docs/infrastructure/README.md | 2 +-
 setup.sh                      | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/infrastructure/README.md b/docs/infrastructure/README.md
index 554f7d93..80503531 100644
--- a/docs/infrastructure/README.md
+++ b/docs/infrastructure/README.md
@@ -90,7 +90,7 @@ sudo bash <(curl -sSL https://raw.githubusercontent.com/oib/aitbc/main/setup.sh)
 ### Manual Setup
 ```bash
 # Clone and setup manually
-sudo git clone https://gitea.bubuit.net/oib/aitbc.git /opt/aitbc
+sudo git clone https://github.com/aitbc/aitbc.git /opt/aitbc
 cd /opt/aitbc
 sudo ./setup.sh
 ```
diff --git a/setup.sh b/setup.sh
index c9f644ef..cdb5ce64 100755
--- a/setup.sh
+++ b/setup.sh
@@ -68,9 +68,9 @@ clone_repo() {
     
     # Clone repository
     cd /opt
-    git clone https://gitea.bubuit.net/oib/aitbc.git aitbc || {
-        # Try alternative URL
-        git clone http://10.0.3.107:3000/oib/aitbc.git aitbc || error "Failed to clone repository"
+    git clone https://github.com/aitbc/aitbc.git aitbc || {
+        # Try alternative GitHub URL
+        git clone git@github.com:aitbc/aitbc.git aitbc || error "Failed to clone repository"
     }
     
     cd /opt/aitbc