Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity
Files
53e061bafd6f5bfdbd5c74b8c9a280a5baf10752
Gitea-Tools/docs/release-workflows.md
T
sysadmin b402de83fe docs: fix trailing whitespace and add approved naming for #52 
Address reviewer blockers on PR #8:
- Remove trailing whitespace in credential-isolation.md and release-workflows.md
- Add approved naming coverage (MCP Control Plane / mcp-control-plane project
  and repo names; common, gitea-mcp, jenkins-mcp, ops-mcp, release-mcp packages)
  to tool-boundaries.md

Documentation-only. No code, scaffolding, or config changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 04:17:30 -04:00

604 B
Raw Blame History

Release Workflows

This document outlines the scope and boundaries of the optional future release-mcp orchestrator.

Orchestrator Role

The release-mcp package may be introduced later to coordinate workflows across the different MCP packages.

  • Coordination, not Consolidation: It can call or compose other tools, but it must not become an all-powerful server holding credentials for all other components.
  • Example Workflows: Tasks such as collecting release evidence, verifying TEST deploy checklists, summarizing state (issue/PR/build/deploy), and posting evidence back to Gitea.
Reference in New Issue View Git Blame Copy Permalink