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

New Issue
Closed
opened 2026-06-06 11:21:21 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-06 11:21:21 +00:00
Owner
Copy Link
Copy Source

Summary

Add tabs above the README rendering on the repository home page for important root-level markdown files, similar to how GitHub displays them. Instead of only showing the README, provide clickable tabs for files like:

  • README.md
  • LICENSE / LICENSE.md
  • CONTRIBUTING.md
  • CODE_OF_CONDUCT.md
  • SECURITY.md
  • CHANGELOG.md

Motivation

GitHub surfaces these files as tabs on the repo landing page, making them easy to discover without browsing the file tree. This improves contributor onboarding and project transparency.

Proposed Behavior

  1. On the repo home page, detect well-known markdown files in the repository root
  2. Display a tab bar above the rendered content (README is the default active tab)
  3. Clicking a tab renders that file inline, replacing the README content area
  4. Only show tabs for files that actually exist in the repo
  5. README tab should always be first if it exists

References

  • GitHub shows LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY as tabs on repo home pages

Authored by Jonathan Miller (@jmiller)

## Summary Add tabs above the README rendering on the repository home page for important root-level markdown files, similar to how GitHub displays them. Instead of only showing the README, provide clickable tabs for files like: - README.md - LICENSE / LICENSE.md - CONTRIBUTING.md - CODE_OF_CONDUCT.md - SECURITY.md - CHANGELOG.md ## Motivation GitHub surfaces these files as tabs on the repo landing page, making them easy to discover without browsing the file tree. This improves contributor onboarding and project transparency. ## Proposed Behavior 1. On the repo home page, detect well-known markdown files in the repository root 2. Display a tab bar above the rendered content (README is the default active tab) 3. Clicking a tab renders that file inline, replacing the README content area 4. Only show tabs for files that actually exist in the repo 5. README tab should always be first if it exists ## References - GitHub shows LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY as tabs on repo home pages --- *Authored by Jonathan Miller (@jmiller)*
jmiller commented 2026-06-06 14:25:44 +00:00
Author
Owner
Copy Link
Copy Source

Testing Complete — All Checks Pass

Tested on dev (git.dev.mokoconsulting.tech) with testadmin/tab-test repo containing all 6 well-known files.

Test Result
All 6 tabs render (readme, license, contributing, code_of_conduct, security, changelog) PASS
License tab shows MIT License content PASS
Security tab shows Security Policy content PASS
Changelog tab shows content PASS
Readme tab active by default PASS
Contributing tab active when selected PASS

Merged to dev via PR #501.

Authored by Jonathan Miller (@jmiller)

## Testing Complete — All Checks Pass Tested on dev (git.dev.mokoconsulting.tech) with testadmin/tab-test repo containing all 6 well-known files. | Test | Result | |------|--------| | All 6 tabs render (readme, license, contributing, code_of_conduct, security, changelog) | PASS | | License tab shows MIT License content | PASS | | Security tab shows Security Policy content | PASS | | Changelog tab shows content | PASS | | Readme tab active by default | PASS | | Contributing tab active when selected | PASS | Merged to dev via PR #501. --- *Authored by Jonathan Miller (@jmiller)*
Sign in to join this conversation.
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 Medium
Type Feature
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#500
Delete Branch "%!s()"

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?