Repository navigation
Templates: Added the theme's name and version to the footer - #173
Merged
Merged
Conversation
The footer links the theme's GitHub repository with its name and version, beside Forgejo's own links. The release build stamps the release tag; other builds show git's description, such as 1.4.0-3-g54b4d73. Admins hide it with --custom-footer-credit: none. 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
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.
Summary
The page footer now credits the theme: GitHub Theme 1.4.0, linking to this repository. It sits after Forgejo's own links (language, Licenses, API) and before any custom footer links, with the same look, hover and phone layout.
THEME_VERSIONto the release tag, andscripts/assembleForgejo.tsstamps it intobase/footer_content.tmpl. Any other build shows whatgit describe --tagssays, such as1.4.0-1-g9482e2ffor a build one commit after 1.4.0, so a development build is never mistaken for a release. Without git it showsdev.--custom-footer-credit: noneto:root, like the other--custom-*switches. It is in the README's CSS variables table.Before and after
The footer of /explore/repos at 1280px (light and dark) and 390px, signed in. The screenshots come from a development build, so the version is git's description of the commit rather than a release number.
With
--custom-footer-credit: none:Release notes
Area: Descriptionwith a listed areaBranches: Fixed ...feature,change,bug,dependencies, orskip-changelogbugonly for a bug that shipped in a release; a fix for a bug that only existed ondevisskip-changelogmajoradded when admins must act on upgrade, for example a new minimum Forgejo version (not needed).github/release-notes.md, if admins need them (not needed)Checks
bun bundle,bun vitest(569 tests) and Prettier pass.bun lintfails ondevas well: typescript-eslint does not support TypeScript 7.🤖 Generated with Claude Code