Vibe coding is already a concern, vibe-approval makes it worse. While an AI could also approve via the mergebot anyway it does add a bit of a hurdle, as the ai can't just use a PAT it might already have for that.
- configuration ui / form on the PR page of the mergebot, going through the current user -> partner_id -> parse_commands (will need to account for not having a comment anymore)
- maybe a web extension to do then do that directly form a PR, and maybe with with a pinned version of the status image
Vibe coding is already a concern, vibe-approval makes it worse. While an AI could also approve via the mergebot anyway it does add a bit of a hurdle, as the ai can't just use a PAT it might already have for that.