Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qodo Merge should be able to respond to multiple commands in one comment #1620

Open
archon810 opened this issue Mar 12, 2025 · 1 comment
Open
Labels

Comments

@archon810
Copy link

Feature request

Qodo Merge should be able to respond and act on multiple commands in a single comment rather than requiring 3 separate comments to achieve this:

/improve
/review
/describe

Motivation

Right now, if you comment with more than one Qodo command, only the first one gets executed. All of them should execute to avoid spamming comments.

@archon810 archon810 added the feature 💡 label Mar 12, 2025
Copy link
Contributor

💡 Auto-generated documentation-based answer:

Based on the current documentation, Qodo Merge does not support executing multiple commands in a single comment. The documentation indicates that commands are executed individually by commenting with specific command formats like /review, /describe, or /improve.

The documentation shows that each tool is triggered separately, either:

  1. Manually by commenting with a single command (e.g., /review, /describe, /improve)
  2. Automatically when a PR is opened by configuring the pr_commands list in the configuration file

There is no mention of the ability to run multiple commands in a single comment. The current behavior matches what you described - only the first command in a comment gets executed, requiring separate comments for each command.

This feature request would be a valid enhancement to reduce comment noise in PRs by allowing users to trigger multiple tools with a single comment.

Relevant Sources:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant