Conversation
marvin-context-protocol
Bot
added
enhancement
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dce3367573
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| WHEN APPLYING too-long: After labeling, post a brief comment using mcp__github__add_issue_comment: | ||
| "Thanks for the report. This issue goes beyond what our contributor guidelines ask for — we just need a short problem description and an MRE. Please see [our pinned guidelines](https://github.com/PrefectHQ/fastmcp/issues/3506) and condense this issue. We'll triage it once it's trimmed down." |
There was a problem hiding this comment.
This new too-long branch instructs Marvin to post a comment via mcp__github__add_issue_comment, but the same prompt still ends with a blanket DO NOT post any comments rule in step 4. In the too-long scenario, these contradictory directives can cause the model to apply the label without posting the required guidance, leaving contributors without the condense instructions and stalling retriage. Make the final no-comment rule explicitly exempt too-long cases so behavior is consistent.
Useful? React with 👍 / 👎.
2 participants
No description provided.