jmiller
86bd8a2cad
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Generic: Repo Health / Site Health (pull_request) Has been skipped
Generic: Repo Health / Access control (pull_request) Successful in 2s
Universal: PR Check / Validate PR (pull_request) Successful in 13s
Generic: Project CI / Lint & Validate (pull_request) Successful in 42s
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 1m18s
PR RC Release / Build RC Release (pull_request) Successful in 1m17s
Universal: Build & Release / Promote to RC (pull_request) Has been skipped
Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped
Universal: PR Check / Secret Scan (pull_request) Successful in 1m32s
Generic: Project CI / Tests (pull_request) Has been cancelled
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Generic: Repo Health / Scripts governance (pull_request) Has been cancelled
Generic: Repo Health / Repository health (pull_request) Has been cancelled
Generic: Repo Health / Report: Scripts Governance (pull_request) Has been cancelled
Generic: Repo Health / Report: Repository Health (pull_request) Has been cancelled
The org "floor" is enforced implicitly at the choke point, so a repo admin couldn't see which org-level rules apply to their repo. Surface them in the repo's Branch Protection settings page (read-only), the way GitHub shows organization rulesets in a repository. - ProtectedBranchRules handler: when the owner is an org, load FindOrgProtectedBranchRules and expose them as OrgProtectedBranches. - branches.tmpl: new read-only "Organization Branch Protection" section listing each org rule with an "Organization" badge, a lock/read-only marker, and compact indicators (required approvals, signed commits, status checks). No edit/delete controls — these are managed at the org level. - en-US locale strings. Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT
MokoGitea
Custom Gitea fork with enhanced wiki system, DLID licensing, issue statuses, cascade merge, security scanning, org metadata, CI standardization, and project board API.
Key Features
- Wiki System -- wikilinks, categories, backlinks, template transclusion, revision diffs, rename redirects, folder ACL, enhanced ToC, print view, ZIP export (details)
- DLID Licensing -- license management, entitlements, domain activations, ed25519-signed downloads
- API Token Scope Editing -- edit token scopes via API (PATCH) or web UI after creation
- Issue Statuses -- custom workflow statuses per org with required baseline protection, presets, cross-org migration
- Cascade Merge -- auto-create PRs to downstream branches after merge with configurable rules per repo
- Security Scanning -- secret detection (pre-receive blocking) + code analysis (SQL injection, XSS, command injection, path traversal, and more) with REST API for alerts, config, and on-demand scans
- Default Org Teams -- auto-create Developers, Reviewers, and CI/CD teams on org creation
- Org Metadata -- per-repo metadata API (public GET, admin PUT), platform detection for versioning
- Branch Protection -- delete allowlist for protected branches (per-user/team/deploy-key)
- Project Board API -- REST endpoints for project columns and cards
- CI Infrastructure -- reusable workflows, centralized ci-issue-reporter, standardized MOKOGITEA_TOKEN naming
- Dev Deploy Gate -- builds deploy to dev environment first, production checks dev health
Documentation
- Org Wiki -- standards, CLI reference, API docs
- Wiki Features -- all 10 wiki enhancements
- Licensing API
- Repo Wiki -- feature docs, API reference, operations
Contributing
See the org wiki for development guidelines, coding standards, and contribution instructions.
License
This project is licensed under the GNU General Public License v3.0 or later -- see the LICENSE file.