chore(links): point the project's links at its Gitea home #166

2026-11-10T23:17:32Z

james.maes commented

2026-11-10 23:17:32 +00:00

What

The project's links point at its Gitea home, https://git.kof22.com/KofTwentyTwo/gclo (public, with the releases and all their assets):

Help menu: "View the project page" (was "View on GitHub"), "Submit an issue", "Community support" (Gitea has no discussions, so it opens the issue list), and the links in the Share invitation.
About dialog, splash screen, and the CLI's "please report it at" line.
README: project page, latest release, the Scoop bucket address, the clone address. CONTRIBUTING / SECURITY: issues and releases.

Why

Closes #165

Left as they are, on purpose

The in-app updater still reads the release feed from where it reads it today. Moving it is a release-pipeline decision and gets its own change.
Links that are about GitHub itself: creating a personal access token, attestation verification, private vulnerability reports, the OpenSSF Scorecard.

How it was tested

Stacked on #164 (the Share item): merge that one first.
Local gates without the UI suite so far: 1014 engine and 212 CLI tests, 100% line coverage, zero warnings, format clean. The UI suite will be run before merge (the smoke test for Share asserts the new release link).
Checked by request: the Gitea project page answers anonymously, /releases/latest redirects to v1.1.0, and that release has the installer, the portable build, the CLI archive, and the update feed.

Checklist

Commits are signed and signed off (git commit -S -s)
Zero build warnings; format and lint are clean
Tests added or updated; the 100% coverage gate still passes
Docs updated for user-visible changes
No secrets, credentials, or personal data
New dependencies are justified below, or none were added (none)
Substantial AI assistance, if any, is noted here: written with Claude Code

🤖 Generated with Claude Code

## What The project's links point at its Gitea home, `https://git.kof22.com/KofTwentyTwo/gclo` (public, with the releases and all their assets): - **Help menu**: "View the project page" (was "View on GitHub"), "Submit an issue", "Community support" (Gitea has no discussions, so it opens the issue list), and the links in the Share invitation. - **About dialog, splash screen**, and the CLI's "please report it at" line. - **README**: project page, latest release, the Scoop bucket address, the clone address. **CONTRIBUTING / SECURITY**: issues and releases. ## Why Closes #165 ## Left as they are, on purpose - The in-app updater still reads the release feed from where it reads it today. Moving it is a release-pipeline decision and gets its own change. - Links that are about GitHub itself: creating a personal access token, attestation verification, private vulnerability reports, the OpenSSF Scorecard. ## How it was tested - Stacked on #164 (the Share item): merge that one first. - Local gates without the UI suite so far: 1014 engine and 212 CLI tests, 100% line coverage, zero warnings, format clean. The UI suite will be run before merge (the smoke test for Share asserts the new release link). - Checked by request: the Gitea project page answers anonymously, `/releases/latest` redirects to v1.1.0, and that release has the installer, the portable build, the CLI archive, and the update feed. ## Checklist - [x] Commits are signed and signed off (`git commit -S -s`) - [x] Zero build warnings; format and lint are clean - [x] Tests added or updated; the 100% coverage gate still passes - [x] Docs updated for user-visible changes - [x] No secrets, credentials, or personal data - [x] New dependencies are justified below, or none were added (none) - [x] Substantial AI assistance, if any, is noted here: written with Claude Code 🤖 Generated with [Claude Code](https://claude.com/claude-code)

james.maes changed target branch from feat/share-invitation to main

2026-11-11 01:35:37 +00:00

james.maes added 2 commits 2026-11-11 01:35:37 +00:00

chore(links): point the project's links at its Gitea home 4be96ce465

The project's home is https://git.kof22.com/KofTwentyTwo/gclo, which is
public and carries the releases with all their assets.

- Help menu: 'View the project page', 'Submit an issue', and 'Community
  support' (Gitea has no discussions, so it opens the issue list) go
  there, and so do the links in the Share invitation.
- About dialog, splash screen, and the CLI's 'please report it at' line.
- README: project page, latest release, the Scoop bucket address, the
  clone address; CONTRIBUTING and SECURITY: issues and releases.

Left as they are: the in-app updater's release feed, and links that are
about GitHub itself (creating a token, attestation verification, private
vulnerability reports, the OpenSSF Scorecard).

Closes #165

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

chore(links): the tracker links, package metadata and release notes follow to Gitea; Help links cannot end the process 03388a35f8

From the independent review: the roadmap and checklist links, TODO.md, the
issue templates, the engine package's metadata, the Chocolatey package's
project links and RELEASING.md still named GitHub. The Help item and its
handler are named for what they open. Opening a page in the browser is
wrapped, because an exception that escapes an event handler ends the process.
The threat model records the move and the Share handoff.

Refs #165

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

james.maes commented

2026-11-11 01:35:58 +00:00

Independent review

Verdict at the first pushed tip: DO NOT MERGE (it was stacked on the Share branch before that branch's fix, and tracker links were left behind). After the fixes: the points below.

Fixed here

The branch is rebased on main, which now carries the Share fixes.
Remaining links moved: roadmap and checklist issues (#7, #11, #62, #66 exist on Gitea under the same numbers), TODO.md, the issue templates, the engine package's RepositoryUrl/PackageProjectUrl and its PACKAGE.md, the Chocolatey package's project links, docs/RELEASING.md.
MenuGitHub / GitHubMenuItem_Click are named for what they open.
Opening a page in the browser no longer lets an exception escape an event handler.
Threat model: a revision row for the move and for the Share handoff.

Checked on the live server: /releases/latest resolves to v1.1.0 with the installer, the portable zip, the CLI zip, the packages and SHA256SUMS; anonymous git ls-remote works (needed for scoop bucket add and the clone line); /issues is public.

Not in this PR, by decision of the owner (next PR): releases and the in-app updater move to Gitea as well. At this commit the updater feed, the release workflow, the package manifests' download URLs, README.md ("GitHub Releases"), SECURITY.md and ADR 0001 still describe GitHub. Velopack's GiteaSource was verified against the live server for both channels.

Left on GitHub on purpose: private vulnerability reporting and security advisories (Gitea has no equivalent), the Scorecard badge, https://github.com/settings/tokens.

Open for the owner: registration on git.kof22.com is closed, so Help > Submit an issue leads someone without an account to a sign-in page they cannot pass. The Share invitation no longer points there.

Gates: build, 1,022 engine and 212 CLI tests, 100% line coverage, format, UI suite 13 of 13.

## Independent review Verdict at the first pushed tip: DO NOT MERGE (it was stacked on the Share branch before that branch's fix, and tracker links were left behind). After the fixes: the points below. **Fixed here** - The branch is rebased on main, which now carries the Share fixes. - Remaining links moved: roadmap and checklist issues (#7, #11, #62, #66 exist on Gitea under the same numbers), `TODO.md`, the issue templates, the engine package's `RepositoryUrl`/`PackageProjectUrl` and its `PACKAGE.md`, the Chocolatey package's project links, `docs/RELEASING.md`. - `MenuGitHub` / `GitHubMenuItem_Click` are named for what they open. - Opening a page in the browser no longer lets an exception escape an event handler. - Threat model: a revision row for the move and for the Share handoff. **Checked on the live server**: `/releases/latest` resolves to v1.1.0 with the installer, the portable zip, the CLI zip, the packages and `SHA256SUMS`; anonymous `git ls-remote` works (needed for `scoop bucket add` and the clone line); `/issues` is public. **Not in this PR, by decision of the owner (next PR):** releases and the in-app updater move to Gitea as well. At this commit the updater feed, the release workflow, the package manifests' download URLs, `README.md` ("GitHub Releases"), `SECURITY.md` and ADR 0001 still describe GitHub. Velopack's `GiteaSource` was verified against the live server for both channels. **Left on GitHub on purpose:** private vulnerability reporting and security advisories (Gitea has no equivalent), the Scorecard badge, `https://github.com/settings/tokens`. **Open for the owner:** registration on git.kof22.com is closed, so Help > Submit an issue leads someone without an account to a sign-in page they cannot pass. The Share invitation no longer points there. **Gates:** build, 1,022 engine and 212 CLI tests, 100% line coverage, format, UI suite 13 of 13.

james.maes merged commit 2deaf1c42a into main

2026-11-11 01:35:59 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#166