From 591d08c6277bc32c1114433276db84d4147e9c57 Mon Sep 17 00:00:00 2001 From: AJ Isaacs Date: Thu, 1 Oct 2026 08:34:01 -0400 Subject: [PATCH] docs: make GitHub the primary repository GitHub (ajisaacs/OpenNest) now owns branches, tags and pull requests. Gitea keeps a read-only pull mirror that syncs hourly and refuses pushes, so PRs merged on GitHub are no longer closed by the old Gitea push mirror. --- AGENTS.md | 2 +- README.md | 2 +- docs/releasing.md | 18 +++++++++--------- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 0d43834..a40bbf7 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -28,7 +28,7 @@ dotnet test OpenNest.WinForms.Tests/OpenNest.WinForms.Tests.csproj Keep desktop-dependent tests in `OpenNest.WinForms.Tests`, never add a WinForms reference to `OpenNest.Tests`. Optional CHR fixtures use local `OpenNest.Tests/test-config.json` and skip when absent. On Linux, build Windows projects with `-p:EnableWindowsTargeting=true`; this is not Windows runtime verification. The headless console builds independently with `dotnet build OpenNest.Console/OpenNest.Console.csproj`. -Releases: follow [the release procedure](docs/releasing.md) and `scripts/Publish-Windows.ps1`; workflow artifacts are candidates, not published releases. Gitea is authoritative for Git refs. +Releases: follow [the release procedure](docs/releasing.md) and `scripts/Publish-Windows.ps1`; workflow artifacts are candidates, not published releases. GitHub (`ajisaacs/OpenNest`) is the primary repository; Gitea is a read-only backup mirror. ## Project map and boundaries diff --git a/README.md b/README.md index e291fcf..56f2219 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ Windows release ZIPs are self-contained: extract the entire archive into a new f ## Build, Test, Run ```bash -git clone https://git.thecozycat.net/aj/OpenNest.git +git clone https://github.com/ajisaacs/OpenNest.git cd OpenNest dotnet build OpenNest.sln # full solution (Windows) dotnet test OpenNest.Engine.Tests/OpenNest.Engine.Tests.csproj # cross-platform engine tests diff --git a/docs/releasing.md b/docs/releasing.md index f16c54f..6c7c03b 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -1,16 +1,16 @@ # Windows releases -Git refs are owned by Gitea (`aj/OpenNest`) and push-mirrored to GitHub -(`ajisaacs/OpenNest`). Create release branches and tags on Gitea, not GitHub. +GitHub (`ajisaacs/OpenNest`) is the primary repository: push branches and tags +there. Gitea (`git.thecozycat.net/aj/OpenNest`) is a read-only backup that +pulls from GitHub every hour; it refuses pushes. ## Build a candidate 1. Choose a committed source revision; never include uncommitted work implicitly. -2. Push a `release/vX.Y.Z` branch containing the release workflow to Gitea and - verify that the push mirror delivered the same commit to GitHub. The mirror's - GitHub credential needs **Contents: read/write** and **Workflows: read/write** - to introduce or update `.github/workflows` files. Do not change credentials - or broaden permissions without the owner's approval. +2. Push a `release/vX.Y.Z` branch containing the release workflow to GitHub. + The pushing credential needs **Contents: read/write**, plus + **Workflows: read/write** to introduce or update `.github/workflows` files. + Do not change credentials or broaden permissions without the owner's approval. 3. The `Windows release build` workflow uses a GitHub-hosted `windows-2022` runner. It builds the solution, runs all four test projects in Release and the main test project in Debug, then packages and smoke-tests the desktop app. @@ -45,8 +45,8 @@ previous packages. CI also exercises this refusal and verifies the ZIP is unchan Review release notes, breaking API changes, and known limitations with the owner. After the candidate passes, integrate the release tooling into the chosen branch, -create an annotated `vX.Y.Z` tag on the exact release commit, push to Gitea, and -verify the same tag/commit on GitHub. Use the successful **tag build's** artifacts +create an annotated `vX.Y.Z` tag on the exact release commit and push it to +GitHub. Use the successful **tag build's** artifacts for the GitHub Release; do not substitute packages built from another commit. Verify the public asset names, sizes, download/checksum, and release status after upload. Do not overwrite an existing release/tag or asset silently.