Approve fix pull requests in the code host, where the review and checks are recorded. A chat button can notify and link, and may be fine for trivial, low risk changes, but it should not replace a reviewer reading the diff or bypass required status checks.
What chat is good at
Chat is quick, visible and low friction. It tells the right people that a fix pull request exists, which saves time compared with waiting for an email.
What chat is poor at
- Showing the diff in enough detail to judge a change.
- Recording who approved, with what identity, in a place auditors expect.
- Enforcing required checks and branch protection.
- Resisting accidents: a button click on a phone is easy to misfire.
Decision table
| Change type | Approve in chat? | Notes |
|---|---|---|
| Patch update to a dev only dependency | Possibly | Only if checks passed and the policy allows |
| Patch update to a runtime dependency | Prefer the code host | Read the diff and changelog |
| Minor or major upgrade | Code host | Needs testing and review |
| Change to build, auth or infrastructure files | Code host | Higher blast radius |
| Anything touching secrets or permissions | Code host | Always a human reviewer |
If you allow chat actions
- Make the button open the pull request, not merge it.
- If it does approve, tie it to the user's own identity in the code host, not a shared bot.
- Require status checks to pass before merge, enforced by branch protection that chat cannot change.
- Limit who may use the button, using the same team list as reviewers.
- Record the action in the pull request and in your audit log.
- Rate limit approvals per person per hour.
Keep the trust model simple
Whatever approves a change should be as strong as a normal review. If the chat route is easier than the review route, people will route around review. Start with notifications, then add actions only where evidence shows they are safe.
For more on limiting what automated fixes can do, read limiting the blast radius of automated fixes and approval tiers for fix pull requests.
Quick check
Can a chat button replace code review?
It should not. Use chat for notice and links, and keep review and required checks in the code host.
Who should be allowed to click an approve button?
Only people who could approve the same change in the code host, acting under their own identity.
Safeguard opens fix pull requests with autonomous remediation off by default and every category on Manual, and you can try a free scan at gold.safeguard.sh/scan.
Last reviewed: 19 October 2026.
