Skip to content

Pull requests: Matched GitHub's list meta lines and commit history rows - #187

Merged
whereareiam merged 1 commit into
devfrom
fix/github-list-meta
Nov 15, 2026
Merged

whereareiam merged 1 commit into
devfrom
fix/github-list-meta

Conversation

@whereareiam

@whereareiam whereareiam commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Summary

A side-by-side pass against GitHub turned up these differences in lists and commit history. All of them now follow GitHub:

  • Pull request and issue lists (repository lists, the dashboard's Issues and Pull requests): the meta line reads like GitHub's, with the author's avatar and name ahead of the event, as in "Fix GitHub-style dashboard and profile menus #8 · alex opened yesterday" and "Add PR-driven release notes #5 · by alex was closed last week". The check icon moves from after the title to this line and shows GitHub's tally of passed checks, "✓ 2/2".
  • Commit history: each day is headed "Commits on Nov 14, 2026". Each row says "committed 3 days ago", or "authored" when someone else committed it. Checks show their tally ("· ✓ 2 / 2"), hashes are cut to seven characters as on GitHub, and the browse button uses GitHub's <> icon. Pull request commit tabs already did the last two.
  • Commit page: the author line reads "committed 3 days ago · ✓ 2/2".

The wording comes from six new phrases in all 31 languages and needs the wording add-on. Without it, these places keep Forgejo's sentences, and only the layout changes: the avatar, the check tally, the short hash and the icon.

Before and after

The pull request list and commit history of the preview's acme/webapp, at 1440px in the dark theme, with the wording add-on. The red crosses are the fixture's failing Actions runs.

Before After
Pull request list with the check icon after the title Pull request list with avatar, event and check tally on the meta line
Commit history with long dates and ten-character hashes Commit history with Commits on headings, committed wording and check tallies

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: repository pull request and issue lists, the dashboard's pull requests, commit history and a commit page

bun check, bun vitest (709 tests) and prettier pass. The colorblind dark theme now sits 59 bytes under the 220 KB size check, so the next stylesheet addition will need that limit raised.

🤖 Generated with Claude Code

Pull request and issue lists put the author's avatar and name before the
event, as in "#8 · user opened yesterday", and count passed checks after
it ("✓ 2/2"). Commit history names each day "Commits on Nov 14, 2026",
words each row "committed" or "authored", counts its checks, shortens
the hash to seven characters and browses with the code icon. The commit
page shares the wording and the count. Six 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 c4ed979 into dev Nov 15, 2026
6 of 7 checks passed
@whereareiam
whereareiam deleted the fix/github-list-meta branch November 15, 2026 16:43
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