chore: update all repo workflows after CLI extraction #65
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Summary
After CLI tools are implemented (issues #56-#64), update auto-release.yml across ALL repos to use the new CLI calls instead of inline bash.
Repos to update
All repos using the universal auto-release workflow template from moko-platform.
Depends on
Scope
All CLI tools are now implemented or confirmed existing on branch
feature/cli-release-tools. This issue remains open to track the workflow refactoring after the CLI tools are merged.Status:
Next: replace inline bash in auto-release.yml with CLI tool calls across all repos.
Completed
pre-release.yml updated across 47 repos
Pushed updated pre-release.yml to all non-MokoGitea repos via Gitea contents API.
Changes:
auto-release.yml Step 8b updated (MokoOnyx)
Replaced inline Python SIGPIPE-prone code with release_body_update.php CLI tool. Pipeline now passes all 22 steps.
Remaining inline bash
Steps 1b, 5, 7, 8 still have inline bash. These are larger blocks that need the corresponding CLI tools to mature before replacement. Tracked but not blocking -- the pipeline works end-to-end.
Repos updated (46/47 + MokoOnyx)
All repos with .mokogitea/workflows/pre-release.yml on main branch. 1 repo (mcp-mokodeploy) was locked/archived.