MokoConsulting/MokoGIT
1
0
Fork 0
Code Issues 148 Pull Requests 2 Releases 96 Wiki Activity

fix(theme): repair broken theme + MokoOnyx surface separation #800

Open
jmiller wants to merge 2 commits from jmiller/fix-theme-config-separation AGit into dev
pull from: jmiller/fix-theme-config-separation
merge into: :dev
Conversation 0 Commits 2 Files Changed 6
+68 -5
jmiller commented 2026-07-17 07:03:03 +00:00
Owner
Copy Link
Copy Source

Fixes the all-white/unstyled theme (stale gitea-* refs) and adds MokoOnyx surface separation: migration 370 (remap saved user themes gitea-->mokogit-), app.example.ini default, and light/dark surface-elevation scale.

Fixes the all-white/unstyled theme (stale gitea-* refs) and adds MokoOnyx surface separation: migration 370 (remap saved user themes gitea-*->mokogit-*), app.example.ini default, and light/dark surface-elevation scale.
jmiller added 2 commits 2026-07-17 07:03:03 +00:00
fix(cli): report 'mokogit version' instead of 'gitea version'
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 10s
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 35s
Details
Generic: Standards Compliance / Secret Scanning (push) Failing after 11s
Details
Generic: Standards Compliance / License Header Validation (push) Successful in 9s
Details
Generic: Standards Compliance / Repository Structure Validation (push) Successful in 10s
Details
Generic: Standards Compliance / Coding Standards Check (push) Successful in 13s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 1m36s
Details
Deploy (Prod) / Build & Deploy to Prod (push) Failing after 1m27s
Details
Generic: Standards Compliance / Workflow Configuration Check (push) Failing after 11s
Details
Generic: Standards Compliance / Documentation Quality Check (push) Successful in 10s
Details
Generic: Standards Compliance / README Completeness Check (push) Failing after 10s
Details
Generic: Standards Compliance / Script Integrity Validation (push) Successful in 11s
Details
Generic: Standards Compliance / Line Length Check (push) Successful in 22s
Details
Generic: Standards Compliance / Version Consistency Check (push) Successful in 1m15s
Details
Generic: Standards Compliance / File Naming Standards (push) Successful in 10s
Details
Generic: Standards Compliance / Insecure Code Pattern Detection (push) Successful in 10s
Details
Generic: Standards Compliance / Git Repository Hygiene (push) Successful in 1m20s
Details
Generic: Standards Compliance / Dead Code Detection (push) Successful in 13s
Details
Generic: Standards Compliance / File Size Limits (push) Successful in 10s
Details
Generic: Standards Compliance / Code Complexity Analysis (push) Successful in 1m12s
Details
Generic: Standards Compliance / TODO/FIXME Tracking (push) Successful in 9s
Details
Generic: Standards Compliance / Code Duplication Detection (push) Successful in 2m25s
Details
Generic: Standards Compliance / Binary File Detection (push) Successful in 1m58s
Details
Generic: Standards Compliance / Broken Link Detection (push) Successful in 13s
Details
Generic: Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 1m47s
Details
Generic: Standards Compliance / API Documentation Coverage (push) Successful in 10s
Details
Generic: Standards Compliance / Accessibility Check (push) Successful in 11s
Details
Generic: Standards Compliance / Performance Metrics (push) Successful in 11s
Details
Generic: Standards Compliance / Unused Dependencies Check (push) Successful in 1m17s
Details
Generic: Standards Compliance / Terraform Configuration Validation (push) Successful in 18s
Details
Generic: Standards Compliance / Enterprise Readiness Check (push) Successful in 1m4s
Details
Generic: Standards Compliance / Repository Health Check (push) Successful in 1m2s
Details
Generic: Project CI / Tests (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Compliance Summary (push) Has been cancelled
Details
7174fd0007 
The CLI app name (cmd/main.go app.Name) was still 'gitea', so `mokogit --version`
and the USAGE/help printed 'gitea version X' and 'gitea doctor ...'. Rename it to
'mokogit' (lower-cased per the USAGE convention) and rebrand the two adjacent Gitea
CLI strings (program description, --work-path usage).

Verified: go build ./cmd/. Does NOT rename the executable file (still /app/gitea/gitea);
that touches Dockerfile/systemd/deploy paths and is a separate, larger change.
fix(theme): repair broken theme + add MokoOnyx surface separation
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 1m0s
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 34s
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 1s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 9s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 53s
Details
Generic: Project CI / Tests (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Details
dee280a98d 
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.
Some required checks failed
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 1m0s
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 34s
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 1s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 9s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 53s
Details
Generic: Project CI / Tests (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Details
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin refs/pull/800/head:jmiller/fix-theme-config-separation
git checkout jmiller/fix-theme-config-separation
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 feature: wiki
Wiki system enhancements
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Priority -
Type -
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#800
Delete Branch "jmiller/fix-theme-config-separation"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?