Repository navigation
Releases: Match GitHub's release details, single-release view and new-release form - #81
Merged
Merged
Conversation
…-release form Compared against GitHub signed in (releases list, a single release, the tags list and the new release form): - The meta line under a release title closes with a divider and the notes start 16px below it, with no extra space above their first heading. - Release notes use filled bullets; the browser gave them the nested hollow style because the notes sit inside a list item. - Draft is a solid grey label. - Asset rows are 45px with 600-weight names and a muted digest. The digest named a font variable that does not exist. - A single release shows a "Releases / title" breadcrumb instead of the Releases/Tags bar and the one-entry release list. - The new and edit release form drops the repository header bar and uses the shared comment editor, 32px fields and buttons. The tags list already matched and is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #79 (base is its branch).
Comparison
Measured against GitHub in a signed-in browser: the releases list, a single release, the tags list and the new release form.
disc)circle)8px 16px, name 14px / 6008px 12px, 7008px 16px, 600Already matching, unchanged: the Releases/Tags switch, search, release list sidebar, 912px release box with 32px gaps, 32px/600 titles, Latest and Pre-release labels; the tags list (header, 90px rows, 16px/600 names, 12px meta).
Not changed:
How
templates/repo/release/list.tmpl: detects a single release from the request path and adds the breadcrumb and a page class.styles/components/repo/release.ts: the measured details; new and edit release form rules on Forgejo's own template (no template override).styles/components/issues/editor.ts: the release form joins the shared editor as an editor-only host, keeping its dashed attachment area as GitHub does.Size
The largest theme file is 224,813 bytes against the 225,280 limit the build test enforces, so there is about 450 bytes of headroom left. The next addition will need space freed first, for example by moving the releases styles out of the main theme file into a page stylesheet loaded by the release templates.
Verification
Checked in the preview: releases list (draft, pre-release, latest, assets open), a single release, the new release form.
bun vitest(403 passed),bun checkand Prettier pass. Screenshots are not attached.🤖 Generated with Claude Code