/agent-merge triggers for unsubmitted reviews
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
### Short summary
Agent-Merge triggers while reviewing pull-quests w/o the review being published
### Affected version or release
v1.1.11
### Installation context
agent-merge
### What happened?
When reviewing a PR on github.com w/ auto-merge active, the copilot starts addressing review comments even though they are still "pending" / not published.
Since the agent will push, this causes the PR diff to change and also means an agent will start prematurely and will work based on false assumptions and incomplete context.
### Steps to reproduce
1. Create a PR
2. Enable agent-merge w/ "address reviews" enabled
3. Start writing review comments on the Web and don't publish
On the next agent-merge run the agent will spin up and prematurely start working.
### Expected behavior
_No response_
### Additional context
- Only recently started to notice this, and it only seems to happen when I review my own PRs.
Contributor guide
Research direction
Start by tracing the agent-merge flow for the “address reviews” option and how it reads GitHub pull-request review state. Reproduce the issue with unpublished pending comments; done means no agent run or push starts until the review is published, while published reviews still trigger normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100