MokoConsulting/Template-Go
Template
1
0
Fork 0
Code Issues 2 Pull Requests 2 Releases Wiki Activity

ci(deploy): drop concurrency blocks so MokoGIT can create deploy runs #18

Merged
jmiller merged 1 commits from fix/drop-deploy-concurrency into main 2026-07-17 04:13:50 +00:00
Conversation 0 Commits 1 Files Changed 3
+21 -9
jmiller commented 2026-07-17 04:13:19 +00:00
Owner
Copy Link
Copy Source

Problem

MokoGIT (the Gitea fork these template repos run on) fails to CREATE a run for any workflow that declares a concurrency: block — both push and workflow_dispatch return 204 but no run is created. Verified empirically in a downstream Go repo (mokoai): commits with the block produced zero deploy runs; removing it restored normal runs (a fresh group name did not help).

Because deploy-dev/rc/prod.yml here are the canonical sync source, the block silently disables deploys in every Go repo it syncs into — and re-adds itself on each sync even after a downstream repo removes it locally.

Change

Remove the concurrency: block from all three deploy workflows. Each keeps a NOTE comment explaining why, so the intent is clear and it isn't reintroduced.

Follow-up (not this PR)

The true root cause is the MokoGIT run-creation bug with concurrency; once that's fixed, the blocks can be restored template-wide.

## Problem MokoGIT (the Gitea fork these template repos run on) **fails to CREATE a run for any workflow that declares a `concurrency:` block** — both `push` and `workflow_dispatch` return 204 but no run is created. Verified empirically in a downstream Go repo (mokoai): commits *with* the block produced zero deploy runs; removing it restored normal runs (a fresh group name did not help). Because `deploy-dev/rc/prod.yml` here are the **canonical sync source**, the block silently disables deploys in every Go repo it syncs into — and re-adds itself on each sync even after a downstream repo removes it locally. ## Change Remove the `concurrency:` block from all three deploy workflows. Each keeps a `NOTE` comment explaining why, so the intent is clear and it isn't reintroduced. ## Follow-up (not this PR) The true root cause is the MokoGIT run-creation bug with concurrency; once that's fixed, the blocks can be restored template-wide.
jmiller added 1 commit 2026-07-17 04:13:19 +00:00
ci(deploy): drop concurrency blocks from deploy-dev/rc/prod (MokoGIT run-creation)
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 16s
Details
Generic: Project CI / Lint & Validate (pull_request) Has been cancelled
Details
Universal: PR Check / Branch Policy (pull_request) Has been cancelled
Details
Universal: PR Check / Secret Scan (pull_request) Has been cancelled
Details
Universal: PR Check / Validate PR (pull_request) Has been cancelled
Details
Generic: Repo Health / Access control (pull_request) Has been cancelled
Details
Generic: Repo Health / Site Health (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Secret Scanning (pull_request) Has been cancelled
Details
Generic: Standards Compliance / License Header Validation (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Repository Structure Validation (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Coding Standards Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Version Consistency Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Workflow Configuration Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Documentation Quality Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / README Completeness Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Git Repository Hygiene (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Script Integrity Validation (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Line Length Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / File Naming Standards (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Insecure Code Pattern Detection (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Code Complexity Analysis (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Code Duplication Detection (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Dead Code Detection (pull_request) Has been cancelled
Details
Generic: Standards Compliance / File Size Limits (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Binary File Detection (pull_request) Has been cancelled
Details
Generic: Standards Compliance / TODO/FIXME Tracking (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Dependency Vulnerability Scanning (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Unused Dependencies Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Broken Link Detection (pull_request) Has been cancelled
Details
Generic: Standards Compliance / API Documentation Coverage (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Accessibility Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Performance Metrics (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Enterprise Readiness Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Repository Health Check (pull_request) Has been cancelled
Details
Generic: Standards Compliance / Terraform Configuration Validation (pull_request) Has been cancelled
Details
Branch Cleanup / Delete merged branch (pull_request) Has been cancelled
Details
Universal: Workflow Sync Trigger / Sync workflows to live repos (pull_request) Has been cancelled
Details
RC Revert / Rename rc/ back to dev/ (pull_request) Has been cancelled
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
Generic: Standards Compliance / Compliance Summary (pull_request) Has been cancelled
Details
db1dc561e7 
MokoGIT (the Gitea fork these template repos run on) fails to CREATE a run for any
workflow that declares a concurrency block: both push and workflow_dispatch return
204 but no run is created. Verified empirically in a downstream Go repo (mokoai) —
commits WITH the block produced zero deploy runs; removing it restored normal runs
(a fresh group name did not help). Because this file is the canonical sync source,
the block silently disables deploys in every Go repo it syncs into.

Remove the block from all three deploy workflows until the MokoGIT concurrency bug
is fixed. Each keeps a NOTE explaining why, so a future sync doesn't reintroduce it.

Claude-Session: https://claude.ai/code/session_015yegaNoxb1SAj2HwZww7z3
jmiller merged commit bb6c6c621a into main 2026-07-17 04:13:50 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
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)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/Template-Go#18
Delete Branch "fix/drop-deploy-concurrency"

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?