Release: org-wide governance series (#727) — dev → main #733

Open

jmiller wants to merge 22 commits from dev into main

pull from: dev

merge into: :main

:main

:feat/org-governance-openapi

:dev

:feature/738-expand-openapi-spec-mcp-tooling-for-org-

:feature/722-cleanup-and-standardization-of-issue-tem

:feature/723-feat-issue-and-pull-request-voting-upvot

:feature/725-enforce-dot-prefixed-repositories-are-al

:feature/727-org-level-branch-protection-is-stored-bu

:feature/secret-scanning

:rc

:rc/v1.26.1-moko.06.07.02

:rc/v1.26.1-moko.06.07.03

:rc/v1.26.1-moko.06.07.01

:rc/v1.26.1-moko.06.07

:rc/v1.26.1-moko.06.06.02

:rc/v1.26.1-moko.06.06.01

:rc/v1.26.1-moko.06.06

:rc/v1.26.1-moko.06.05.01

:rc/v1.26.1-moko.06.05

:rc/v1.26.1-moko.06.04

:rc/v1.26.1-moko.06.03

:rc/05.06.00

:rc/05.03.03

:rc/04.01.00

:rc/05.03.02

:rc/05.03.01

:rc/05.03.00

:rc/05.01.00

:rc/05.02.02

:rc/05.02.01

:rc/05.01.01

:rc/05.02.00

:rc/05.01.02

:rc/05.03.04

:rc/05.03.05

:rc/05.03.06

:rc/05.03.08

:rc/05.04.00

:rc/05.05.00

Conversation 0 Commits 22 Files Changed 43

+1979 -73

jmiller commented 2026-07-05 04:37:45 +00:00

Owner

Copy Link

Copy Source

Promotes the org-wide governance series (issue #727) from dev to main. This is the consolidation of the five stacked PRs already merged to dev (#728–#732).

Contents (dev over main: 13 commits)

• #728 Org branch protection — layers with per-repo rules (most-restrictive, fail-closed) + delete-protection ability + read-only inherited-rules view
• #729 Org tag protection — team-allowlist, layered at the push/delete + release paths + read-only view
• #730 Org push policy — pre-receive enforcement: ref-name conventions, mandatory secret-block, max file size, blocked paths (content checks fail-open)
• #731 Org repo defaults — force-private + PR-unit defaults applied via notifier on repo create/transfer
• #732 Org email domain policy — membership restricted to allowed email domains at the AddTeamMember choke point
• Migrations 362–366 (contiguous after main's 361); one unrelated pre-existing dev commit (issue-template edit)

Validation status (please read before merging)

• Deep-dive review done (pre-merge, on the integrated tree): 3 independent adversarial reviewers + a security pass — all symbols resolve, no import cycles, notifier signatures match, all 37 branch-protection fields merged with no loosening. One gofmt issue (trailing struct-field comments) was found and fixed.
• CI on dev's tip: Lint & Validate, Validate PR, Secret Scan, Branch Policy all passed. The Project CI / Tests job stayed stuck "Blocked by required conditions" — the chronic runner-queue stall, not a code failure — so a definitive go test run is still owed. Recommend kicking the runners for a clean Tests pass before merging to main.
• Known follow-ups (not blockers): regenerate swagger for the new org endpoints; repo-facing read-only views for push-policy & repo-defaults (they're org-wide configs, readable via API).

Merging this cuts a stable release to main. Review below.

https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Promotes the **org-wide governance series** (issue #727) from `dev` to `main`. This is the consolidation of the five stacked PRs already merged to `dev` (#728–#732). ## Contents (dev over main: 13 commits) - **#728** Org branch protection — layers with per-repo rules (most-restrictive, fail-closed) + delete-protection ability + read-only inherited-rules view - **#729** Org tag protection — team-allowlist, layered at the push/delete + release paths + read-only view - **#730** Org push policy — pre-receive enforcement: ref-name conventions, mandatory secret-block, max file size, blocked paths (content checks fail-open) - **#731** Org repo defaults — force-private + PR-unit defaults applied via notifier on repo create/transfer - **#732** Org email domain policy — membership restricted to allowed email domains at the `AddTeamMember` choke point - Migrations **362–366** (contiguous after main's 361); one unrelated pre-existing `dev` commit (issue-template edit) ## Validation status (please read before merging) - **Deep-dive review done** (pre-merge, on the integrated tree): 3 independent adversarial reviewers + a security pass — all symbols resolve, no import cycles, notifier signatures match, all 37 branch-protection fields merged with no loosening. One gofmt issue (trailing struct-field comments) was found and fixed. - **CI on `dev`'s tip:** `Lint & Validate`, `Validate PR`, `Secret Scan`, `Branch Policy` all **passed**. The `Project CI / Tests` job stayed stuck "Blocked by required conditions" — the chronic runner-queue stall, **not** a code failure — so a definitive `go test` run is still owed. Recommend kicking the runners for a clean Tests pass before merging to main. - **Known follow-ups (not blockers):** regenerate swagger for the new org endpoints; repo-facing read-only views for push-policy & repo-defaults (they're org-wide configs, readable via API). Merging this cuts a stable release to `main`. Review below. https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

jmiller added 13 commits 2026-07-05 04:37:48 +00:00

Update .mokogitea/ISSUE_TEMPLATE/feature_request.md 343cba690e

fix(org): layer org-level branch protection with repo rules, most-restrictive wins (#727) ... 24b3516c1d

Org-level branch protection was already consulted at the single enforcement
choke point `GetFirstMatchProtectedBranchRule`, but only as a FALLBACK: if any
repo-level rule matched the branch, the org rule was ignored entirely. That let
a repo define a looser rule for a pattern and effectively opt out of the org's
protection.

Make the choke point LAYER the two rules instead: when both an org rule and a
repo rule match a branch, return their most-restrictive (fail-closed)
combination, so the org rule is a mandatory floor a repo can only tighten.

- models/git/protected_branch_merge.go: mergeMostRestrictive + helpers. Allow
  flags AND'd; gate/require/block flags OR'd; RequiredApprovals max'd; required
  sets (status contexts, protected files) unioned; allow sets (whitelists,
  unprotected files) intersected. A disabled allowlist means "everyone", so it
  only constrains when enabled.
- models/git/protected_branch_list.go: GetFirstMatchProtectedBranchRule now
  fetches both the repo rule and the org rule and merges when both match;
  returns whichever exists when only one matches. Org lookup factored into
  getFirstMatchOrgProtectedBranchRule.

Supersedes the materialization approach previously proposed for this issue —
the org fallback already existed, so only this one function needed to change.

Fail-closed by design: any merge edge errs toward MORE protection (over-restrict)
rather than less, so it cannot open a hole.

Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here —
relying on CI to validate build, formatting, and tests.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

feat(org): show inherited org branch-protection rules in repo settings (#727) ... 86bd8a2cad

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

feat(org): add branch-deletion protection + expandable inherited-rule view (#727) ... 4b68853f08

Two related additions:

1. Branch deletion as an org-level ability. OrgProtectedBranch gained
   CanDelete / EnableDeleteAllowlist / DeleteAllowlistTeamIDs (migration 362),
   ToProtectedBranch maps them, and the API (create/edit/response DTOs +
   handlers) exposes enable_delete / enable_delete_allowlist /
   delete_allowlist_teams. The layering merge already combined delete fields, so
   org delete-protection now enforces once ToProtectedBranch populates them.

2. The repo Branch Protection view now renders each inherited org rule as an
   expandable detail (direct push, force-push, branch deletion, merge, required
   approvals, status checks, protected files) with team names resolved, instead
   of three headline badges. Still read-only.

Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here.
Verified by hand: struct-field gofmt alignment, template block nesting balances,
every .Rule field exists on OrgProtectedBranch, and all locale keys referenced
in the template are defined.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

feat(org): org-level tag protection, layered with per-repo protected tags (#727) ... b31336d1fe

Adds org-level tag protection as a parallel to org-level branch protection.
An org tag rule is {NamePattern, AllowlistTeamIDs}; it cascades to every repo
in the org and layers on top of the repo's own protected tags — a tag is
controllable (push/delete) only if allowed at BOTH levels (fail-closed).

- models/git/org_protected_tag.go: OrgProtectedTag model + CRUD +
  ToProtectedTag() (reuses the ProtectedTag matcher/allowlist logic) +
  IsUserAllowedToControlTagInRepo() which ANDs the repo decision with the org
  decision. Migration 363.
- API: /orgs/{org}/tag_protections CRUD (routers/api/v1/org/tag_protection.go,
  DTOs in modules/structs/org_tag.go, wired in api.go).
- Enforcement: the git push/delete hook (hook_pre_receive.go) and the two
  release paths (release.go create/delete) now call the layered check, so no
  per-site tag logic changes beyond swapping the helper.
- View: the repo Tag settings page lists inherited org tag rules read-only.

Stacked on #728 (branch-protection PR) for migration ordering — merge #728
first. Swagger annotations omitted (can't regenerate the swagger JSON without
the toolchain); routes still register.

Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here.
Hand-verified: gofmt (tabs, no blank-in-block, struct alignment), template
nesting balances, all .Rule fields exist on OrgProtectedTag, all locale keys
defined, JSON valid, migration contiguous (363).

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

feat(org): org-level push policy enforced in the pre-receive hook (#727) ... 3aac1b456c

Adds a single per-org push policy that cascades to every repo of the org and is
enforced in the pre-receive hook:

- Branch/tag name conventions (glob) — a pushed ref name must match. Fail-closed.
- Mandatory secret-scanning block-on-push — org can force secret blocking that a
  repo cannot disable (overrides the per-repo scanner config in the orchestrator).
- Max pushed-file size — rejects a tip tree containing a blob over the limit.
- Blocked file-path patterns — rejects pushes changing matching paths (reuses
  pull_service.CheckFileProtection).

The two content checks (blocked paths, max size) FAIL OPEN on any error so a
policy/parsing bug can never wedge all pushes; naming is fail-closed.

- models/git/org_push_policy.go: OrgPushPolicy model + CRUD + matchers +
  GetOrgPushPolicyForRepo. Migration 364.
- API: GET/PATCH/DELETE /orgs/{org}/push_policy (routers/api/v1/org/push_policy.go,
  DTOs in modules/structs/org_push_policy.go, wired in api.go).
- Enforcement: routers/private/hook_pre_receive.go (branch: naming + blocked paths
  + max size; tag: naming) and services/security/orchestrator.go (secret mandate).

Deferred: a repo-facing read-only view of the org push policy (it is an org-wide
config, not per-repo overlay rules; readable via the API for now).

Stacked on #729/#728 for migration ordering (this = 364). Swagger annotations
omitted (can't regenerate without the toolchain).

Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here.
Hand-verified: gofmt (tabs, no blank-in-block), escape sequences in the ls-tree
parser, imports used, migration contiguous (364), fail-open on content checks.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

feat(org): org-level repository defaults applied on repo create/transfer (#727) ... d3134b1c53

Adds a single per-org repository-defaults config, applied to a repo when it is
created in or transferred into the org via a notifier (services/org):

- ForcePrivate — force new/transferred repos private (Repository.IsPrivate).
- PR defaults (when ApplyPRDefaults) — allowed merge styles, default merge
  style, and auto-delete-branch-after-merge, written to the repo's pull-requests
  unit config via repo_service.UpdateRepositoryUnits.

Best-effort: the notifier logs and swallows errors, so a defaults bug can never
break repository creation or transfer.

- models/git/org_repo_defaults.go: OrgRepoDefaults model + CRUD + migration 365.
- API: GET/PATCH/DELETE /orgs/{org}/repo_defaults.
- services/org/notifier.go: CreateRepository/TransferRepository -> apply defaults;
  registered from routers/init.go (org_service.Init()).

Stacked on #730/#729/#728 for migration ordering (this = 365). Swagger omitted.

Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here.
Hand-verified: gofmt (tabs, no blank-in-block, struct/DTO alignment), imports
used, no Init() collision in services/org, migration contiguous (365), notifier
signatures match the Notifier interface.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

feat(org): org-level email domain policy for members (#727) ... 6a3db171c1

Restricts which email domains an organization's members may have. When a policy
is configured, a user can only be added to the org (via any team) if their
primary email matches one of the allowed domain globs.

Enforced at the single membership choke point services/org.AddTeamMember, which
every add path (API, web, group-sync) funnels through — so one check covers them
all. On violation it returns a typed ErrEmailDomainNotAllowed; the API team-add
handler maps it to 422.

- models/git/org_email_domain.go: OrgEmailDomainPolicy model + EmailAllowed
  (domain glob match) + OrgEmailDomainAllowed + typed error + CRUD. Migration 366.
- API: GET/PATCH/DELETE /orgs/{org}/email_domain_policy.
- Enforcement in services/org/team.go; 422 mapping in routers/api/v1/org/team.go.

An empty policy imposes no restriction. This is the one bounded piece of the
"access/security" tier; org 2FA-required and IP allowlists were deliberately NOT
built here — they are cross-cutting enforcement (auth gating / request
middleware) that needs a compiler + tests, not a blind stacked PR.

Stacked on #731/#730/#729/#728 for migration ordering (this = 366). Swagger
omitted.

Note: no Go toolchain available locally, so not compiled/gofmt'd/tested here.
Hand-verified: gofmt (tabs, no blank-in-block), imports (git_model added to the
api team handler, gci order), typed-error detection, migration contiguous (366).

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Merge pull request 'fix(org): layer org-level branch protection with repo rules — most-restrictive wins (#727)' (#728) from fix/727-materialize-org-branch-protection into dev 37fb3703c7

Merge pull request 'feat(org): org-level tag protection, layered with per-repo protected tags (#727)' (#729) from feat/org-tag-protection into dev 3a5c6a37cf

Merge pull request 'feat(org): org-level push policy enforced in the pre-receive hook (#727)' (#730) from feat/org-push-policy into dev 02071a23d6

Merge pull request 'feat(org): org-level repository defaults applied on repo create/transfer (#727)' (#731) from feat/org-repo-defaults into dev 45fc346d52

Merge pull request 'feat(org): org-level email domain policy for members (#727)' (#732) from feat/org-email-domain into dev aeed197ea5

jmiller referenced this issue from a commit 2026-07-05 04:40:21 +00:00

chore: remove stray package-lock.json accidentally committed to dev

jmiller referenced this pull request 2026-07-05 04:40:37 +00:00

chore: remove stray package-lock.json accidentally committed to dev #734

jmiller added 2 commits 2026-07-05 04:41:11 +00:00

chore: remove stray package-lock.json accidentally committed to dev ... bd821e2d44

package-lock.json (13.9k lines of generated npm lockfile) was swept into the
org push-policy commit (3aac1b456c, #730) by a `git add -A` during a gofmt-fix
restack. It is not tracked on main and is not part of the org-governance work.
Removing it so the dev -> main promotion (#733) doesn't introduce it.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Merge pull request 'chore: remove stray package-lock.json accidentally committed to dev' (#734) from chore/remove-stray-package-lock into dev d07cfd412b

jmiller referenced this issue from a commit 2026-07-05 05:07:06 +00:00

fix: repair build (renamed org-visibility helper) + gofmt

jmiller referenced this pull request 2026-07-05 05:07:34 +00:00

fix: repair build (renamed org-visibility helper) + gofmt #735

jmiller added 2 commits 2026-07-05 05:08:12 +00:00

fix: repair build (renamed org-visibility helper) + gofmt ... 125eefc650

Two pre-existing issues surfaced when the org-governance series was compiled
locally with a real Go toolchain (go1.26.3) for the first time:

- routers/api/v1/api.go:519 called organization.HasOrgOrUserVisible, which no
  longer exists — it was renamed to IsOwnerVisibleToDoer (models/organization/
  org.go:548, identical signature). This one missed call site meant the whole
  routers/api/v1 package (and therefore the server binary) failed `go build`.
  With the rename, `go build ./...` is clean.
- gofmt: api.go (a mis-indented commented-out /projects route block) and
  release.go (import sort: repo before updateserver) were gofmt-dirty. Fixed
  with gofmt -w on the two files this change already touches.

Not part of #727, but blocks building/releasing the fork; found while validating
the dev -> main promotion (#733).

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Merge pull request 'fix: repair build (renamed org-visibility helper) + gofmt' (#735) from fix/compile-hasorgvisible-and-gofmt into dev 63f773aa56

jmiller added 3 commits 2026-07-05 05:58:56 +00:00

fix: repair pre-existing test-suite compile/vet failures ... 5d797431f0

`go vet ./...` (finally runnable with a local Go toolchain) surfaced three
pre-existing failures that prevented the whole test tree from compiling — which
is very likely why the "Project CI / Tests" job never went green. None relate to
#727; all pre-existing on main.

- modules/util/util_test.go: CryptoRandomInt/String/Bytes now return (value,
  error); the tests used single-value assignment. Updated to capture + assert
  the error (and dropped a now-redundant `var err error`).
- tests/integration/auth_oauth2_test.go: `newFakeOIDCServer` was declared twice
  with different signatures (redeclaration = build failure). Renamed the
  config-struct variant to `newFakeOIDCServerWithConfig` and updated its caller;
  the (sub, oid) variant keeps the original name for its caller.
- routers/web/repo/issue_comment.go: removed a redundant `&& statusIDStr != ""`
  duplicate condition (vet: redundant and).

Verified: `go vet ./modules/util` clean; full `go vet ./...` re-run.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

fix: partial repair of tests/integration compile errors (license test) ... 948e7bcd21

api_license_keys_test.go used the outdated NewRequestWithBody signature
(passing []byte where io.Reader is now required) — wrapped the string bodies in
strings.NewReader. Note: tests/integration remains broadly pre-existing-broken
across multiple other fork-added files (api_packages_composer type mismatch,
etc.); those are a separate dedicated cleanup, not part of #727.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Merge pull request 'fix: repair unit-test compile + vet failures (partial integration cleanup)' (#736) from fix/vet-test-suite-blockers into dev 89ed32e961

jmiller referenced this pull request 2026-07-05 06:09:01 +00:00

fix(ci): pass TAG/REGISTRY_TOKEN into remote shell in dev deploy #737

jmiller added 2 commits 2026-07-05 06:15:13 +00:00

fix(ci): pass TAG/REGISTRY_TOKEN into remote shell in dev deploy ... 3917bf6a29

The dev deploy step used an unquoted SSH heredoc and referenced
runner-side values as \$TAG / \$REGISTRY_TOKEN, deferring their
expansion to the remote shell where those names are unset. The
Docker build tag collapsed to "mokogitea:" and every dev deploy
failed with `invalid tag ... invalid reference format` before any
migration or server boot could run.

Inject TAG and REGISTRY_TOKEN as an env prefix on the ssh command
(`TAG='...' REGISTRY_TOKEN='...' bash -s`) and switch to a quoted
heredoc so every $var expands in exactly one place: the remote host.
Also fixes HEALTH_FMT (was defined on the runner but referenced
remotely) and adds an explicit empty-TAG guard so a future
regression fails loudly instead of building an untagged image.

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Merge pull request 'fix(ci): pass TAG/REGISTRY_TOKEN into remote shell in dev deploy' (#737) from fix/deploy-dev-var-expansion into dev 2713c49aec

jmiller referenced this pull request 2026-07-05 06:23:58 +00:00

Expand OpenAPI spec + MCP tooling for org-governance endpoints (#727 series) #738

jmiller referenced this pull request 2026-07-05 07:01:31 +00:00

docs(api): OpenAPI spec + README/CHANGELOG for org-governance (#727, #738) #739

Some required checks failed

Hide all checks

Universal: PR Check / Branch Policy (pull_request) Successful in 2s

Details

Generic: Repo Health / Access control (pull_request) Successful in 2s

Details

Generic: Repo Health / Site Health (pull_request) Has been skipped

Details

Universal: PR Check / Validate PR (pull_request) Successful in 13s

Details

Generic: Project CI / Lint & Validate (pull_request) Successful in 35s

Details

Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 1m13s

Details

Universal: Build & Release / Promote to RC (pull_request) Has been skipped

Details

Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped

Details

PR RC Release / Build RC Release (pull_request) Successful in 2m48s

Details

Universal: PR Check / Secret Scan (pull_request) Successful in 2m49s

Details

Deploy MokoGitea (Dev) / Build & Deploy to Dev (push) Failing after 4m55s

Details

Universal: Auto Version Bump / Version Bump (push) Has been skipped

Details

Generic: Project CI / Tests (pull_request) 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: Scripts Governance (pull_request) Has been cancelled

Details

Generic: Repo Health / Report: Repository Health (pull_request) Has been cancelled

Details

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin dev:dev

git checkout dev

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

feature: wiki

Wiki system enhancements

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

bug

Something is not working

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-Fork#733