5.5 Pipelines (DevOps)
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 149
Description
# 5.5 Pipelines (DevOps)
**Parent:** Story 5 (#7232)
**Tool file:** new `forge/ee/lib/mcp/tools/pipelines.js`
## Summary
Expose DevOps pipelines so agents can inspect and drive CI/CD. The headline capability is **deploy** (push a stage to the next). Feature-flagged by license tier. Reads ship first; pipeline and stage mutations, including deploy, follow in phase 2, and destructive deletes are isolated behind `destructiveHint: true`.
Contributor guide
Research direction
Start with the new forge/ee/lib/mcp/tools/pipelines.js tool file and review how existing MCP tools expose license-gated capabilities and destructiveHint metadata. Define the read operations first, then determine the phase-2 pipeline, stage, deploy, and delete mutations; done means the pipeline capabilities are exposed with the stated feature-flag and destructive-operation boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100