MokoConsulting/MokoGitea-Fork
1
0
Fork 0
Code Issues 174 Pull Requests Releases 96 Wiki Activity

Support GitHub-style org and user profile repos (.github, .profile) #651

New Issue
Open
opened 2026-06-19 07:43:40 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-19 07:43:40 +00:00
Owner
Copy Link
Copy Source

Summary

GitHub uses .github and .github-private repos for org-level profile READMEs and community health files. MokoGitea uses .mokogitea and .mokogitea-private equivalents, but should also alias the GitHub naming convention so that:

  • .github works as an alias for the org profile repo (currently org-profile / .mokogitea)
  • .github-private works as an alias for private org config
  • .profile works for user-level profile READMEs

Current Behavior

MokoGitea only recognizes .mokogitea-prefixed repo names for org/user profiles.

Expected Behavior

Both .github and .mokogitea naming conventions should be recognized, with .mokogitea taking priority if both exist. This ensures compatibility with repos migrated from GitHub and reduces friction for users familiar with GitHub conventions.

Context

Our GitHub backup mirrors map org-profile → .github and .mokogitea-private → .github-private. Having MokoGitea natively support both naming patterns would eliminate the need for these name translations.

## Summary GitHub uses `.github` and `.github-private` repos for org-level profile READMEs and community health files. MokoGitea uses `.mokogitea` and `.mokogitea-private` equivalents, but should also alias the GitHub naming convention so that: - `.github` works as an alias for the org profile repo (currently `org-profile` / `.mokogitea`) - `.github-private` works as an alias for private org config - `.profile` works for user-level profile READMEs ## Current Behavior MokoGitea only recognizes `.mokogitea`-prefixed repo names for org/user profiles. ## Expected Behavior Both `.github` and `.mokogitea` naming conventions should be recognized, with `.mokogitea` taking priority if both exist. This ensures compatibility with repos migrated from GitHub and reduces friction for users familiar with GitHub conventions. ## Context Our GitHub backup mirrors map `org-profile` → `.github` and `.mokogitea-private` → `.github-private`. Having MokoGitea natively support both naming patterns would eliminate the need for these name translations.
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-Fork#651
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?