22175 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jmiller	c74173bb86	ci(deploy-rc): add workflow_dispatch for isolated manual tests ... Lets deploy-rc be run on demand (from a ref carrying current source) to verify the RC pipeline end-to-end without a full rc promotion + pre-release. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 19:15:55 -05:00
jmiller	b2447da3dd	Merge pull request 'feat(ci): deploy-rc.yml — auto-deploy rc branch to the new RC environment' (#751) from feat/deploy-rc-workflow into dev	2026-07-06 00:03:55 +00:00
jmiller	7be712571c	refactor(ci): tier-scope deploy-rc variables (RC_SSH_*, RC_REGISTRY*, RC_IMAGE) ... Shared DEPLOY_HOST/PORT/USER assumed all tiers live on one host. Scope every deploy variable to the rc tier (mirrors the org's DEV_SSH_* convention) so a repo inheriting this template can host rc/dev/prod on separate machines independently. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 19:01:38 -05:00
jmiller	6634b049ab	fix(ci): deploy-rc reuses existing DEPLOY_SSH_KEY + MOKOGITEA_TOKEN secrets ... The registry token is the org-wide MOKOGITEA_TOKEN secret (already configured, used by deploy-dev/deploy-mokogitea), not a new DEPLOY_REGISTRY_TOKEN. Reuse the existing secret names so no new secret values are needed; only the non-sensitive tier variables get set per-repo. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 18:54:27 -05:00
jmiller	5c62cefcd3	refactor(ci): deploy-rc.yml -> root workflows, fully parameterized via repo vars/secrets ... - Moved from custom/ to the root .mokogitea/workflows/ (synced/template-owned area). - All deployment config now comes from repo Actions variables (DEPLOY_HOST/PORT/USER, DEPLOY_REGISTRY/IMAGE, RC_CONTAINER/COMPOSE_PROJECT/COMPOSE_DIR/SOURCE_DIR/TAG_ENV/ HEALTH_URL) and secrets (DEPLOY_SSH_KEY, DEPLOY_REGISTRY_TOKEN) — nothing hardcoded, so it works across Go server repos. Clone URL derived from github.server_url/repository. - To become Template-Go-owned (Template-Go#3). Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 18:37:33 -05:00
jmiller	f2ca569906	feat(ci): deploy-rc.yml — auto-deploy the rc branch to the RC environment ... Adds a custom deploy workflow that builds and deploys the release candidate to rc.git.mokoconsulting.tech (mokogitea-rc container, port 3110, DB mokogitea_rc) on push to the rc branch — the branch promote-rc creates when a PR to main is opened. Mirrors the fixed deploy-dev.yml: env-var image tag (MOKOGITEA_RC_TAG) driving the shared compose file (no sed), rm -f before force-recreate, quoted-heredoc remote expansion, health check + external verify. Gives a real release-candidate environment to validate before prod. Intended to move to Template-Go as the canonical synced source once validated (kept in custom/ for now so it isn't overwritten by workflow sync). Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 18:31:51 -05:00
jmiller	b9301a8f31	Merge pull request 'feat: org branch protection per-user (username/email) allowlists + actions-bot toggle (#727)' (#750) from feature/org-branch-protection-user-allowlists into dev	2026-07-05 22:54:30 +00:00
jmiller	cac06c2ac7	feat: org branch protection per-user allowlists + Actions-bot toggle (#727) ... Extend org-level branch protection to support per-user allowlists (resolved from username OR email) and an "allow Actions bot" toggle, alongside the existing team allowlists, for all five categories (push, merge, force-push, delete, approvals). - models/git/org_protected_branch.go: add WhitelistUserIDs, MergeWhitelistUserIDs, ForcePushAllowlistUserIDs, DeleteAllowlistUserIDs, ApprovalsWhitelistUserIDs ([]int64) plus WhitelistActionsUser, MergeWhitelistActionsUser, ForcePushAllowlistActionsUser, DeleteAllowlistActionsUser (bool); copy all 9 into ProtectedBranch in ToProtectedBranch(). - models/migrations/v1_27/v368.go: migration 367 adds the 9 columns. - modules/structs/org_branch.go: add *Usernames []string and *ActionsUser bool to Create/Edit options and the response, matching repo-level json names. - routers/api/v1/org/branch_protection.go: resolveUserIDs (username then email, dedupe, 422 on unknown); wire into Create + Edit and toAPIOrgBranchProtection. - models/git/protected_branch_merge.go: add mergeAllowFlag and merge the four Actions-user flags most-restrictively (org can now express them); deploy-key flags stay repo-only pass-through. - models/git/protected_branch_merge_test.go: mergeAllowFlag truth table, user-ID intersection, deploy-key pass-through. - regenerate swagger v1 + openapi3 specs. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 17:48:47 -05:00
jmiller	6c0c2c3f1f	Merge pull request 'chore(sync): cascade main -> dev' (#748) from main into dev	2026-07-05 22:03:31 +00:00
jmiller	4db6f03efd	Merge fix/rebrand-wiki-docs: normalize in-repo wiki branding	2026-07-05 22:01:50 +00:00
jmiller	bdac121b70	docs(wiki): normalize in-repo wiki branding (MokoGitea/mokocli/MokoStandards->org wiki/MokoSuite)	2026-07-05 22:01:47 +00:00
jmiller	80a4c68063	chore: sync workflow-sync-trigger.yml from Template-Generic [skip ci]	2026-07-05 21:46:31 +00:00
jmiller	5c0bf5f214	chore: sync version-set.yml from Template-Generic [skip ci]	2026-07-05 21:46:18 +00:00
jmiller	e2f8d5ce9b	chore: sync repo-health.yml from Template-Generic [skip ci]	2026-07-05 21:46:08 +00:00
jmiller	1d5427f2c2	chore: sync rc-revert.yml from Template-Generic [skip ci]	2026-07-05 21:45:58 +00:00
jmiller	9d949b6294	chore: sync pre-release.yml from Template-Generic [skip ci]	2026-07-05 21:45:45 +00:00
jmiller	515e8fcdea	chore: sync pr-check.yml from Template-Generic [skip ci]	2026-07-05 21:45:34 +00:00
jmiller	519966015b	chore: sync notify.yml from Template-Generic [skip ci]	2026-07-05 21:45:24 +00:00
jmiller	2677caafd6	chore: sync issue-branch.yml from Template-Generic [skip ci]	2026-07-05 21:45:14 +00:00
jmiller	66148f76fa	chore: sync gitleaks.yml from Template-Generic [skip ci]	2026-07-05 21:45:05 +00:00
jmiller	7a4be6ab63	chore: sync cleanup.yml from Template-Generic [skip ci]	2026-07-05 21:44:56 +00:00
jmiller	c26ceaea87	chore: sync ci-issue-reporter.yml from Template-Generic [skip ci]	2026-07-05 21:44:50 +00:00
jmiller	8ba2dbf3e3	chore: sync cascade-dev.yml from Template-Generic [skip ci]	2026-07-05 21:42:28 +00:00
jmiller	44b25099ac	chore: sync branch-cleanup.yml from Template-Generic [skip ci]	2026-07-05 21:42:21 +00:00
jmiller	838d1f0d28	chore: sync auto-release.yml from Template-Generic [skip ci]	2026-07-05 21:42:15 +00:00
jmiller	6e0db30b3e	chore: sync auto-bump.yml from Template-Generic [skip ci]	2026-07-05 21:42:09 +00:00
jmiller	e2343c8fb4	chore: sync workflow-sync-trigger.yml from Template-Generic [skip ci]	2026-07-05 21:09:03 +00:00
jmiller	8e045c60fc	chore: sync pr-check.yml from Template-Generic [skip ci]	2026-07-05 21:08:49 +00:00
jmiller	d3a0c7534b	chore: sync version-set.yml from Template-Generic [skip ci]	2026-07-05 20:43:30 +00:00
jmiller	7f0da28988	chore: sync sync-on-merge.yml from Template-Generic [skip ci]	2026-07-05 20:43:14 +00:00
jmiller	6cd1d10617	chore: sync repo-health.yml from Template-Generic [skip ci]	2026-07-05 20:42:59 +00:00
jmiller	5c8056f15e	chore: sync rc-revert.yml from Template-Generic [skip ci]	2026-07-05 20:42:42 +00:00
jmiller	ffaa3662e6	chore: sync pre-release.yml from Template-Generic [skip ci]	2026-07-05 20:42:24 +00:00
jmiller	1c462f9d49	chore: sync pr-check.yml from Template-Generic [skip ci]	2026-07-05 20:42:05 +00:00
jmiller	8fbf97ac7e	chore: sync gitleaks.yml from Template-Generic [skip ci]	2026-07-05 20:41:46 +00:00
jmiller	b3448f4d62	chore: sync ci-issue-reporter.yml from Template-Generic [skip ci]	2026-07-05 20:41:21 +00:00
jmiller	f72300a03f	chore: sync cascade-dev.yml from Template-Generic [skip ci]	2026-07-05 20:40:53 +00:00
jmiller	08a43ec718	chore: sync branch-cleanup.yml from Template-Generic [skip ci]	2026-07-05 20:40:04 +00:00
jmiller	bf2b299f87	chore: sync auto-release.yml from Template-Generic [skip ci]	2026-07-05 20:39:44 +00:00
jmiller	89aa805967	chore: sync auto-bump.yml from Template-Generic [skip ci]	2026-07-05 20:39:24 +00:00
jmiller	3efbab985b	Merge pull request 'fix(locale): duplicate en-US key crashes boot under jsonv2 (#696/#728)' (#743) from fix/locale-dup-key-jsonv2 into dev	2026-07-05 20:32:07 +00:00
jmiller	98b1ed2f7b	fix(locale): duplicate en-US key crashes server boot under jsonv2 ... The branch-protection delete feature (#696/#728) added a second "repo.settings.event_delete" entry ("Branch Deletion") to locale_en-US.json, reusing the existing webhook-event key (value "Delete"). The old JSON decoder silently kept the last value; Go 1.26's jsonv2 decoder rejects duplicate object keys, so InitLocales fails ("duplicate object member name repo.settings.event_delete") and the server crash-loops at startup. Like the code-scanner regexp panic, this only surfaces on a fresh boot, which is why it shipped unnoticed. Give the branch-protection section header its own key "repo.settings.protect_branch_deletion" and point protected_branch.tmpl at it, so the webhook "Delete" label and the branch-protection "Branch Deletion" header both render correctly and the JSON has no duplicate. Verified: no duplicate keys remain in any options/locale/*.json. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 15:21:31 -05:00
jmiller	ccfc9a604b	Merge pull request 'fix(security): code scanner RE2 lookahead panics server at startup (#552)' (#742) from fix/code-scanner-re2-panic into dev	2026-07-05 20:07:45 +00:00
jmiller	2f119fbd95	fix(security): code scanner panics at startup on RE2-incompatible regexp ... The "deserialize-yaml-py" rule in services/security/code_scanner.go used a negative lookahead `(?!\s*#)` in regexp.MustCompile. Go's regexp engine is RE2, which has no lookahead/lookbehind, so MustCompile panics during the package init() — crash-looping the entire server at startup. `go build` and `go vet` do not execute init(), and CI never boots the binary, so this shipped to main via #552 undetected; the running instances survived only because they predate that image. Replace the pattern with an RE2-safe equivalent `(?i)yaml\.load\s*\(`, which matches the rule's stated intent (flag yaml.load() without SafeLoader, CWE-502). Add a regression test that forces the package init and asserts every DefaultCodeRules pattern compiled, so a future RE2-incompatible pattern fails in CI here instead of on a live deploy. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 15:06:57 -05:00
jmiller	7f229ba01c	Merge pull request 'fix: org-governance release review findings + dev deploy targeting (#727, #733)' (#741) from fix/org-governance-review into dev	2026-07-05 19:51:06 +00:00
jmiller	e98fca780e	fix: address org-governance release review (#727, #733) + dev deploy targeting ... Code-review findings on the org-governance release: - Fail closed on org-rule lookup error: getFirstMatchProtectedBranchRule swallowed FindOrgBranchRuleForBranch errors (returned nil,nil), silently dropping the org floor and falling back to the repo rule on a transient DB error. Propagate the error so the org rule stays enforced. - Stop the org rule locking out deploy-key and Actions-bot pushes: OrgProtectedBranch is team-only, so mergeMostRestrictive was ANDing the repo's WhitelistDeployKeys / WhitelistActionsUser (and the force-push, delete and merge counterparts) against the org side's always-false zero value, blocking every deploy-key and Actions push in any org with a matching branch rule. Carry those org-unmanaged fields through from the repo rule unchanged. - Org push-policy max-file-size now inspects only the pushed delta (diff-tree + cat-file --batch-check) instead of the full tip tree via ls-tree, so a pre-existing oversized file can no longer permanently block unrelated pushes. New branches (no base commit) still scan the full tree. Dev deploy targeting: - deploy-dev.yml drove the dev container image via `sed` on the SHARED compose file, but the pattern matched the *prod* service line (container_name: mokogitea) — leaving the dev service pinned to a stale image (so every "green" deploy recreated old code) while corrupting the prod image pin. Drive the dev service image from ${MOKOGITEA_DEV_TAG} instead; the env-var only affects the dev service. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 14:46:01 -05:00
jmiller	7a4dc5e809	Merge pull request 'docs(api): OpenAPI spec + README/CHANGELOG for org-governance (#727, #738)' (#739) from feat/org-governance-openapi into dev	2026-07-05 15:19:08 +00:00
jmiller	8c63b00953	Merge pull request 'fix(ci): recreate dev container to avoid name conflict on deploy' (#740) from fix/deploy-dev-container-conflict into dev	2026-07-05 15:18:53 +00:00
jmiller	6b81922c47	fix(ci): recreate dev container to avoid name conflict on deploy ... After the tag fix (#737) the dev deploy builds and pushes the image fine but fails at `docker compose up -d` with: Conflict. The container name "/mokogitea-dev" is already in use The dev service uses a fixed container_name, and the symlinked /opt/gitea-dev path makes compose's derived project name unstable, so an existing container is not recognized as the project's and `up` tries to create rather than recreate. Remove any lingering fixed-name container first, pin the compose project name, and force a fresh recreate so migrations run against the new image. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 10:17:08 -05:00
jmiller	93365cdd95	docs(api): swagger annotations + response models for org-governance endpoints (#727, #738) ... Annotate the four previously undocumented org-governance API handlers (tag_protection, push_policy, repo_defaults, email_domain) with swagger:operation blocks, and register the swagger:response models the branch_protection operations already referenced. Register the org option DTOs in the parameterBodies hack so their definitions are emitted. Also fix pre-existing spec-generation blockers surfaced once the spec became regenerable: a stray comment glued to the repoUpdateManifest swagger block (broke YAML parsing), missing owner/repo path params on the manifest operations, a Manifest response registration, and missing definitions for EditAccessTokenOption, the IssueBulk* options, and the Issue{Priority,Status,Type}Def types. Regenerated v1_json.tmpl and v1_openapi3_json.tmpl; spec now validates cleanly against Swagger 2.0. Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT	2026-07-05 01:58:08 -05:00