Short summary
PR not linked to session
Affected version or release
v0.2.5
Installation context
No response
What happened?
This happens to me on every other PR. Very annoying for obvious reasons.
The MCP function the agent tries to use to open the PR fails with 422, apparently because we work off of forks and can't create branches on the main repo. Then, it usually asks me if it is allowed to use gh to open the PR, and I approve. But it's about 50-50 on whether the PR actually gets linked. I've had some sessions try to update whatever local DB state is missing the linkage but that never helped either.
Happy to provide examples for investigation if it helps.
Steps to reproduce
No response
Expected behavior
PR gets linked
Additional context
Happy to provide IDs if you tell me how to retrieve them.
Short summary
PR not linked to session
Affected version or release
v0.2.5
Installation context
No response
What happened?
This happens to me on every other PR. Very annoying for obvious reasons.
The MCP function the agent tries to use to open the PR fails with 422, apparently because we work off of forks and can't create branches on the main repo. Then, it usually asks me if it is allowed to use
ghto open the PR, and I approve. But it's about 50-50 on whether the PR actually gets linked. I've had some sessions try to update whatever local DB state is missing the linkage but that never helped either.Happy to provide examples for investigation if it helps.
Steps to reproduce
No response
Expected behavior
PR gets linked
Additional context
Happy to provide IDs if you tell me how to retrieve them.