Purpose-Built tool to Bridge my GitHub Repos to a Forgejo Repo.
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-03 01:57:21 +01:00
.env.example Make a small debug capture scaffold 2026-11-03 01:44:30 +01:00
.gitignore Make a small debug capture scaffold 2026-11-03 01:44:30 +01:00
README.md Initial Commit 2026-11-03 01:08:53 +01:00
requirements.txt Make a small debug capture scaffold 2026-11-03 01:44:30 +01:00
scaffold.py Include Headers on Capture 2026-11-03 01:57:21 +01:00

GitHub-Bridge

A purpose-built tool to connect my personal Git Server's Repositories to my GitHub Repositories.

From my initial planning, here's what I came up with:

  1. Host some sort of server that holds both my GitHub and Forgejo Application Keys
  2. Have a (either locally or WAN with Auth) exposed API that allows me to POST a new Bridge. (Refer to here)

For now though, this is only this document.

TODO

  • Create API Scaffold
  • Store created Bridges
  • Find some way to capture GitHub/Forgejo Issue events (Maybe Webhooks?)
  • Extend it to PRs (Create remote Branch on the corresponding side)
  • A lot of other stuff I can't think of right so ask me again later

What I imagine the API-Endpoints to be

  • GET /bridge-api -> Return every existing Link (needs some sort of object store or db)
  • POST /bridge-api {"gh":(GitHub Repo URL), "fj":(Forgejo Repo URL)} -> Create a new Bridge
  • DELETE /bridge-api/(Bridge ID) -> Remove existing Bridge