Commonwealth-Online-Server

6 Commits

Include renames

Author	SHA1	Message	Date
Nomads_Reach	8258affc22	ops: restore Gitea sync workflow after deployment attempt	2026-08-18 14:33:48 -04:00
Nomads_Reach	0cc4c0e4d4	ops: use sync runner for fleet deployment	2026-08-18 14:24:42 -04:00
Nomads_Reach	9c5c16caf8	Disable Git credential helpers during Gitea sync	2026-08-17 16:02:56 -04:00
Nomads_Reach	30142c9706	Move Gitea sync to isolated trusted runner and stop persisting token	2026-08-17 15:52:19 -04:00
Nomads_ReachandGitHub	098cf34355	Run the Gitea sync workflow on the self-hosted runner (#23 ) Acceptance (end-to-end TCP) / End-to-end TCP acceptance (push) Canceled after 0s Details CSharp Server Gate / Repository policy, C# build and test (push) Canceled after 0s Details GNS Transport Bridge / Linux native GNS bridge (push) Canceled after 0s Details Host GUI (Avalonia) / Build Avalonia host (push) Canceled after 0s Details Acceptance (end-to-end TCP) / End-to-end TCP acceptance (pull_request) Canceled after 0s Details CSharp Server Gate / Repository policy, C# build and test (pull_request) Canceled after 0s Details GNS Transport Bridge / Linux native GNS bridge (pull_request) Canceled after 0s Details Host GUI (Avalonia) / Build Avalonia host (pull_request) Canceled after 0s Details GitHub-hosted runners are billing-blocked for this org, so the hosted open-gitea-pr job never started (empty logs, immediate failure on every push to main). Retarget it to [self-hosted, Linux, X64] like the other workflows; the runner has LAN access to the Gitea host, and this workflow only fires on push to main, so it never runs untrusted fork PR code.	2026-08-16 20:07:37 -04:00
NomadsReach	34fb54990c	Open a Gitea PR automatically when main is merged on GitHub	2026-08-15 20:53:03 -04:00