docs: decide which host the CHANGELOG release links target #393
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis#393
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The link references in
CHANGELOG.md([0.1.0],[Unreleased]) point atgithub.com/felis-terminal/felis/{compare,releases/tag}. Release assets, however, are published by the Forgejorelease.yml, anddocs/how-to/install.mdsays to "Open the release page … on Forgejo". README calls GitHub a mirror, and the mirror receives tags, so the GitHubreleases/tagpage may show a bare tag with no assets.Decide which host the changelog links target (git.natsukium.com releases/compare, or GitHub as the public face). If GitHub stays, decide whether the mirror should also carry releases. The release gate (
tools/release/verify.py) should check whichever form is chosen.Decision: the CHANGELOG link references target the public Forgejo repository at
https://git.natsukium.com/felis-terminal/felis(releases/tag/v…andcompare/…), where the release assets are published.tools/release/verify.pychecks that form.Closing: the CHANGELOG keeps pointing at the GitHub mirror, which main already does. PR #448 was closed unmerged.