fix: allowlist oz-for-x[bot] for issue triage#480
Conversation
When oz-for-x files an issue (create_issue action), the triage agent should run by default. Previously the bot was dropped by the bot-author guard since it wasn't on the allowlist. Co-Authored-By: Oz <oz-agent@warp.dev>
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds oz-for-x[bot] to .github/oz/config.yml under triage.bot_author_allowlist, matching the existing allowlist shape for bot-authored issue triage.
Concerns
No blocking general, security, or spec-drift concerns were found. The attached spec context reports that no approved or repository spec context exists for this PR.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
2 participants
Add
oz-for-x[bot]totriage.bot_author_allowlistso issues filed by the X/Twitter feedback integration get triaged by default.Previously the bot was silently dropped by the bot-author guard in
_route_issues()because it wasn't on the allowlist.warp-dev-github-integration[bot](Slack) was added in #477 butoz-for-x[bot]was missed.Conversation: https://staging.warp.dev/conversation/17dde216-e767-40f0-94cb-803461110163
Run: https://oz.staging.warp.dev/runs/019eadd7-8e4a-7435-8bba-f7719fd9272f
This PR was generated with Oz.