GitHub to Gitea Link Mapping

GitHub to Gitea Link Mapping

Purpose: Maintain authenticity by replacing GitHub links with self-hosted Gitea equivalents where possible, and documenting external dependencies that must remain on GitHub.

Status: Living document - updated as repos are mirrored to Gitea

Badlucksbane-Owned Repositories

These repositories are owned by Badlucksbane and should be mirrored to Gitea for full self-hosted authenticity.

✅ Already on Gitea

🟡 To Be Mirrored to Gitea

Action Required:

• Mirror these repositories to Gitea
• Update all content links to use Gitea URLs
• Ensure CI/CD workflows are updated

External Dependencies (Must Remain on GitHub)

These repositories are external projects that Badlucksbane depends on but does not own. They must remain on GitHub as we cannot mirror them without permission.

LLM Backends & Inference Engines

Development Tools

Documentation & Community

Link Replacement Guidelines

For Badlucksbane Repositories

Pattern: Replace https://localhost:3000/benbrown/{repo} with http://localhost:3000/benbrown/{repo}

Examples:

• https://localhost:3000/benbrown/epistemic-kernel → http://localhost:3000/benbrown/epistemic-kernel
• https://localhost:3000/benbrown/epistemic-kernel/releases → http://localhost:3000/benbrown/epistemic-kernel/releases
• https://localhost:3000/benbrown/epistemic-kernel/discussions → http://localhost:3000/benbrown/epistemic-kernel/discussions

For External Dependencies

Keep as-is but add documentation noting:

• The dependency is external and cannot be self-hosted
• Why it’s required (e.g., “Primary LLM inference engine”)
• License information

For GitHub-Specific Features

Some features are inherently tied to GitHub:

1. Giscus: Uses GitHub Discussions/Issues as backend. Currently requires external GitHub accounts. Note in content: “Requires external GitHub accounts (external dependency)”
2. GitHub Releases: Can be replaced with Gitea Releases once repos are mirrored
3. GitHub Actions: Can be replaced with Gitea Actions once repos are mirrored

Verification Checklist

• All badlucksbane GitHub links identified
• External dependencies documented
• Gitea mirrors created for owned repos
• Content links updated to use Gitea
• External dependencies clearly marked
• Link validation script created

Link Validation

A script to validate that no GitHub links exist for Badlucksbane-owned content:

#!/bin/bash
# validate-links.sh - Check for GitHub links that should be Gitea

GITHUB_BADLUCKSBANE="localhost:3000/benbrown"
GITEA_HOST="http://localhost:3000"

# Find all markdown files in content
echo "Checking for Badlucksbane GitHub links..."
grep -r "$GITHUB_BADLUCKSBANE" badlucksbane-site/content/ 2>/dev/null || echo "No Badlucksbane GitHub links found (good!)"

# Check for specific external deps that are allowed
echo -e "\nAllowed external dependencies:"
echo "  - ggerganov/llama.cpp (external LLM backend)"
echo "  - oobabooga/text-generation-webui (external tool)"
echo "  - petals-inference/petals (external tool)"

Run this script periodically to ensure no regressions.

Migration Plan

Phase 1: Immediate (This Task)

1. ✅ Document all GitHub links
2. ✅ Create this mapping document
3. ⏳ Update content to note external dependencies
4. ⏳ Add link validation documentation

Phase 2: Short Term (1-2 weeks)

1. Create Gitea mirrors for epistemic-kernel and friend repos
2. Update all content links to use Gitea
3. Update download/community links

Phase 3: Long Term (Ongoing)

1. Set up automated sync from GitHub to Gitea (if needed)
2. Migrate CI/CD to Gitea Actions
3. Consider replacing Giscus with self-hosted alternative (Remark42)

Last updated: 2026-08-08 Maintainer: Aurora (COO) Related: Audit Finding benbrown-wmq