MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 3 Releases 96 Wiki Activity

feat(ui): tabbed view for root markdown files alongside README (#500) #501

Merged
jmiller merged 1 commits from feat/500-root-file-tabs into dev 2026-06-06 11:50:21 +00:00
Conversation 0 Commits 1 Files Changed 4
+123
jmiller commented 2026-06-06 11:48:34 +00:00
Owner
Copy Link
Copy Source

Summary

  • Add tabs above the README on the repo home page for well-known root files (LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG)
  • Tabs only appear when both a README and at least one other well-known file exist
  • Clicking a tab renders that file inline, replacing the README content
  • Similar to how GitHub surfaces these files for easy discovery

Closes #500

Test Plan

  • Verify tabs appear on repo home page with README + well-known files
  • Click each tab and verify content renders correctly
  • Verify tabs don't appear on repos with only README
  • Verify tabs don't appear in subdirectory views
  • Check no regressions in standard README rendering

Authored by Jonathan Miller (@jmiller)

## Summary - Add tabs above the README on the repo home page for well-known root files (LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG) - Tabs only appear when both a README and at least one other well-known file exist - Clicking a tab renders that file inline, replacing the README content - Similar to how GitHub surfaces these files for easy discovery Closes #500 ## Test Plan - [ ] Verify tabs appear on repo home page with README + well-known files - [ ] Click each tab and verify content renders correctly - [ ] Verify tabs don't appear on repos with only README - [ ] Verify tabs don't appear in subdirectory views - [ ] Check no regressions in standard README rendering --- *Authored by Jonathan Miller (@jmiller)*
jmiller added 1 commit 2026-06-06 11:48:35 +00:00
feat(ui): tabbed view for root markdown files alongside README (#500)
Generic: Repo Health / Site Health (push) Has been skipped
Details
Generic: Repo Health / Access control (push) Successful in 1s
Details
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 1s
Details
Generic: Repo Health / Access control (pull_request) Successful in 1s
Details
PR RC Release / Build RC Release (pull_request) Successful in 3s
Details
Universal: PR Check / Validate PR (pull_request) Failing after 6s
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 1s
Details
Generic: Repo Health / Scripts governance (push) Has been cancelled
Details
Generic: Repo Health / Repository health (push) Has been cancelled
Details
Generic: Repo Health / Report Issues (push) 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: Repo Health / Scripts governance (pull_request) Has been cancelled
Details
Generic: Repo Health / Repository health (pull_request) Has been cancelled
Details
Generic: Repo Health / Report Issues (pull_request) Has been cancelled
Details
9313ae2731 
Add tabs above the README rendering on the repo home page for well-known
root files (LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG),
similar to how GitHub surfaces these files for easy discovery.

Tabs only appear when both a README and at least one other well-known file
exist. Clicking a tab renders that file inline, replacing the README.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit b9937fabd9 into dev 2026-06-06 11:50:21 +00:00
jmiller deleted branch feat/500-root-file-tabs 2026-06-06 11:50:22 +00:00
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
 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
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/MokoGitea-APP#501
Delete Branch "feat/500-root-file-tabs"

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?