jmiller
dee280a98d
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 1m0s
Generic: Project CI / Lint & Validate (pull_request) Successful in 34s
Universal: PR Check / Branch Policy (pull_request) Successful in 1s
Universal: PR Check / Validate PR (pull_request) Successful in 9s
Universal: PR Check / Secret Scan (pull_request) Successful in 53s
Generic: Project CI / Tests (pull_request) Has been cancelled
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Branch Cleanup / Delete merged branch (pull_request) Successful in 2s
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
The MokoGitea->MokoGIT branding rebrand deleted the gitea-* theme CSS and
shipped only theme-mokogit-{auto,light,dark}.css, but two things were left
pointing at the retired themes, producing an unstyled "all white" page with an
invisible navbar theme toggle:
1. Users' saved `user.theme` still held gitea-* names, whose CSS now 404s.
Add migration 370 (RemapGiteaThemesToMokogit) to rewrite each user's saved
theme gitea-{auto,light,dark}(-colorblind) -> mokogit-* equivalent,
preserving their light/dark/auto preference. Idempotent.
2. app.example.ini still documented DEFAULT_THEME = gitea-auto. Correct it to
mokogit-auto so fresh installs start on a shipped theme. (The running
servers' app.ini [ui] THEMES/DEFAULT_THEME are fixed operationally.)
Also address the flat "all white / no separation" look by adding a MokoOnyx
surface-separation scale to both themes (mokoconsulting.tech gray scale):
- light: soft gray page (#f0f3f6) so white cards/boxes lift off it, gray-200
box headers, stronger gray-300 border definition.
- dark: 3-step navy-tinted elevation (page #0b1017 -> box #121a24 -> header
#17212e) cohesive with the #112855 brand nav, more visible panel edges.
The auto theme @imports light/dark, so it inherits both automatically.