Skip to content

feat: add environment lifecycle and pipeline trigger tools - #691

Open
Agent-Hellboy wants to merge 1 commit into
zereight:mainfrom
Agent-Hellboy:feat/environments-triggers-682-clean
Open

feat: add environment lifecycle and pipeline trigger tools#691
Agent-Hellboy wants to merge 1 commit into
zereight:mainfrom
Agent-Hellboy:feat/environments-triggers-682-clean

Conversation

@Agent-Hellboy

Copy link
Copy Markdown
Contributor

Closes #682.

Adds environment update/delete/stop/stale-stop/review-app cleanup and pipeline trigger list/get/create/update/delete/run operations.

Validation: npm run build; git diff --check.

@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 31 minutes.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 77871c41-1ab8-4bc1-8655-f63542d073ba

📥 Commits

Reviewing files that changed from the base of the PR and between 1f7e8f4 and 4185f00.

📒 Files selected for processing (4)
  • index.ts
  • schemas.ts
  • skills/gitlab-mcp/reference/pipelines.md
  • tools/registry.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Agent-Hellboy
Agent-Hellboy force-pushed the feat/environments-triggers-682-clean branch 2 times, most recently from a375f90 to eb3fbda Compare August 26, 2026 14:41
@Agent-Hellboy
Agent-Hellboy force-pushed the feat/environments-triggers-682-clean branch from eb3fbda to 4185f00 Compare August 26, 2026 14:44
@zereight

Copy link
Copy Markdown
Owner

Question on stop_stale_environments: it's registered in both destructiveTools and deleteTools, so GITLAB_PERMISSION_MODE=modify blocks it. It stops environments, it doesn't delete anything — other non-delete write actions like merge/protect/push are allowed in modify mode.

Was blocking it in modify intentional (since it can stop many environments at once), or should it move out of deleteTools to match the merge/protect/push precedent?

@zereight zereight left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stop_stale_environments is registered in both destructiveTools and deleteTools, so GITLAB_PERMISSION_MODE=modify blocks it — but it stops environments, it doesn't delete anything. Other non-delete write actions (merge/protect/push) are allowed in modify mode. Please confirm whether blocking it in modify is intentional, or move it out of deleteTools to match that precedent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Environment lifecycle and pipeline triggers

2 participants