Skip to content

Repository: Matched GitHub's labels, milestones, tags and branch counts - #188

Merged
whereareiam merged 1 commit into
devfrom
fix/github-pages-pass
Nov 15, 2026
Merged

whereareiam merged 1 commit into
devfrom
fix/github-pages-pass

Conversation

@whereareiam

@whereareiam whereareiam commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Summary

A second side-by-side pass against GitHub covered labels, milestones, tags and the repository home. These now follow GitHub:

  • Labels: a label's open issues show as GitHub shows them, an icon and the number, with Forgejo's full sentence in the tooltip. Labels with no open issues show nothing, as on GitHub, instead of "0 open issues/pull requests".
  • Milestones: the description comes right under the title, followed by GitHub's line "Due by December 14, 2026 • 0/3 issues closed". The progress reads "0% complete · 3 open · 0 closed" in GitHub's case. Before, the row had a calendar icon with a short date and "Updated yesterday" above the description.
  • Tags: the box gets GitHub's "🏷 Tags" header row. Hashes are cut to seven characters, and a tag's release is linked as "📄 Notes" instead of "Release details".
  • Repository home: the counts read "11 Branches" and "4 Tags", capitalised as on GitHub.

The wording comes from nine new phrases in all 31 languages and needs the wording add-on. Without it, these places keep Forgejo's text, and only the layout changes: the icon-only label counts, the milestone order, the tags header, the short hashes and the Notes icon.

Before and after

The preview's acme/webapp at 1440px in the dark theme, with the wording add-on.

Before After
Labels with open issue sentences Labels with icon and number counts
Milestone with calendar date and Updated Milestone with Due by line and issues closed
Tags without a header and with long hashes Tags with header row, short hashes and Notes

Release notes

  • The title follows Area: Description with a listed area
  • The title describes the effect in the past tense, for example Branches: Fixed ...
  • Exactly one label: feature, change, bug, dependencies, or skip-changelog
  • bug only for a bug that shipped in a release; a fix for a bug that only existed on dev is skip-changelog
  • major added when admins must act on upgrade, for example a new minimum Forgejo version
  • Upgrade steps or warnings added to .github/release-notes.md, if admins need them

Checks

  • Tests added or updated
  • Checked in the dev preview: labels, open and closed milestones, tags and the repository home

bun check, bun vitest (709 tests) and prettier pass. The theme stylesheets did not grow; the tags header lives in the releases page stylesheet.

🤖 Generated with Claude Code

Label rows count open issues by icon and number and show nothing for
none. Milestone rows put the description first, then "Due by November
30, 2026 • 3/7 issues closed", with "complete", "open" and "closed"
in GitHub's case. The tags box gets GitHub's header row, seven-character
hashes and a "Notes" link. The repository home says "11 Branches" and
"4 Tags". Nine new phrases in all 31 languages; without the add-on
Forgejo's wording stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@whereareiam whereareiam added the change Changed look, templates or compatibility label Nov 15, 2026
@whereareiam
whereareiam merged commit e6cfee3 into dev Nov 15, 2026
6 of 7 checks passed
@whereareiam
whereareiam deleted the fix/github-pages-pass branch November 15, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

change Changed look, templates or compatibility

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant