Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 6 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Document LLM-operated Gitea workflow runbooks #17

New Issue
Closed
opened 2026-07-01 11:16:16 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-01 11:16:16 -05:00
Owner
Copy Link
Copy Source

Parent

Roadmap #10 — Task-scoped MCP execution profiles for LLM-operated Gitea workflows

Scope

Create documentation/runbooks for common LLM-operated Gitea workflows:

  • create issue
  • create child issues
  • implement issue and open PR
  • review PR
  • request changes
  • approve PR
  • merge PR
  • close issue after merge
  • stop on blocker

The runbooks should explain that roles are task-scoped and profile-based.

Required content

Include examples such as:

Use any eligible reviewer profile to review PR #N.
Use any eligible merger profile to merge PR #N if checks pass.
Use an author profile to implement issue #N and open a PR.

Document required fail-closed behavior:

  • unknown identity
  • unknown profile
  • authenticated user equals PR author
  • PR head changed
  • unexpected files changed
  • secrets detected
  • production/deploy behavior detected

Acceptance criteria

  • Runbooks exist.
  • Runbooks use the MCP Control Plane naming.
  • Runbooks explain task-scoped profiles.
  • Runbooks explain that LLMs are not permanently assigned roles.
  • Runbooks include safe prompts for issue creation, PR review, and merge.
  • No implementation code is added.

Non-goals

  • Do not implement tooling in this docs issue.
  • Do not add Jenkins/Ops/deploy behavior.

Proposed labels

mcp · gitea · documentation · runbook · dogfooding

## Parent Roadmap #10 — Task-scoped MCP execution profiles for LLM-operated Gitea workflows ## Scope Create documentation/runbooks for common LLM-operated Gitea workflows: * create issue * create child issues * implement issue and open PR * review PR * request changes * approve PR * merge PR * close issue after merge * stop on blocker The runbooks should explain that roles are task-scoped and profile-based. ## Required content Include examples such as: ```text Use any eligible reviewer profile to review PR #N. Use any eligible merger profile to merge PR #N if checks pass. Use an author profile to implement issue #N and open a PR. ``` Document required fail-closed behavior: * unknown identity * unknown profile * authenticated user equals PR author * PR head changed * unexpected files changed * secrets detected * production/deploy behavior detected ## Acceptance criteria * Runbooks exist. * Runbooks use the MCP Control Plane naming. * Runbooks explain task-scoped profiles. * Runbooks explain that LLMs are not permanently assigned roles. * Runbooks include safe prompts for issue creation, PR review, and merge. * No implementation code is added. ## Non-goals * Do not implement tooling in this docs issue. * Do not add Jenkins/Ops/deploy behavior. ## Proposed labels `mcp` · `gitea` · `documentation` · `runbook` · `dogfooding`
jcwalker3 added the mcpgiteadocumentation labels 2026-07-01 11:28:30 -05:00
jcwalker3 added the status:in-progress label 2026-07-02 00:21:26 -05:00
jcwalker3 commented 2026-07-02 00:21:41 -05:00
Author
Owner
Copy Link
Copy Source

Claimed. Starting documentation/finalization pass.

Branch: docs/issue-17-runtime-profile-docs.

Scope: LLM-operated Gitea workflow runbooks (task-scoped, profile-based roles; create/review/request-changes/approve/merge/close; stop-on-blocker; fail-closed rules) plus canonical config + interactive menu + thin-launcher + migration docs. Docs-only, no implementation code. Safe examples only.

Claimed. Starting documentation/finalization pass. Branch: `docs/issue-17-runtime-profile-docs`. Scope: LLM-operated Gitea workflow runbooks (task-scoped, profile-based roles; create/review/request-changes/approve/merge/close; stop-on-blocker; fail-closed rules) plus canonical config + interactive menu + thin-launcher + migration docs. Docs-only, no implementation code. Safe examples only.
sysadmin removed the status:in-progress label 2026-07-02 01:31:23 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
chore
documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 important
mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
read-only
Read-only, no mutation
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
No Label documentation gitea mcp
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#17
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?