feat: org-wide .mokogitea repo for shared workflows and issue templates #223

New Issue

2026-05-26T20:23:43Z

jmiller commented

2026-05-26 20:23:43 +00:00

Summary

Allow organizations to create a special .mokogitea repository that provides default workflow files and issue/PR templates to all repos in the org -- similar to GitHub .github repository convention.

Motivation

With 37+ repos across MokoConsulting, maintaining identical workflow files (e.g. auto-release.yml) and issue templates in every repo is tedious and error-prone. A single org-level repo would provide:

Shared workflow files: Repos without their own .gitea/workflows/ would inherit from the org .mokogitea repo
Shared issue/PR templates: Default templates applied to all org repos that do not define their own
Single point of update: Change a workflow once, all repos pick it up

Proposed Behavior

If an org has a repo named .mokogitea, Gitea checks it for:
- workflow-templates/ -- reusable workflow files
- ISSUE_TEMPLATE/ -- default issue templates
- PULL_REQUEST_TEMPLATE/ -- default PR templates
Repo-level files take precedence over org-level defaults
Org admins control the .mokogitea repo; regular members can read but not modify

References

GitHub .github repository: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file
Gitea already supports .gitea directory per-repo; this extends the concept to org level

Opened by Claude Code on behalf of @jmiller

## Summary Allow organizations to create a special `.mokogitea` repository that provides default workflow files and issue/PR templates to all repos in the org -- similar to GitHub `.github` repository convention. ## Motivation With 37+ repos across MokoConsulting, maintaining identical workflow files (e.g. auto-release.yml) and issue templates in every repo is tedious and error-prone. A single org-level repo would provide: - **Shared workflow files**: Repos without their own `.gitea/workflows/` would inherit from the org `.mokogitea` repo - **Shared issue/PR templates**: Default templates applied to all org repos that do not define their own - **Single point of update**: Change a workflow once, all repos pick it up ## Proposed Behavior 1. If an org has a repo named `.mokogitea`, Gitea checks it for: - `workflow-templates/` -- reusable workflow files - `ISSUE_TEMPLATE/` -- default issue templates - `PULL_REQUEST_TEMPLATE/` -- default PR templates 2. Repo-level files take precedence over org-level defaults 3. Org admins control the `.mokogitea` repo; regular members can read but not modify ## References - GitHub `.github` repository: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file - Gitea already supports `.gitea` directory per-repo; this extends the concept to org level --- *Opened by Claude Code on behalf of @jmiller*

Sign in to join this conversation.

Status —

Type Feature

Status —

Priority —

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#223