Triage from GitHub
Anyone with write access to a repository can triage the issues Dam Secure raises on a pull request by replying to its inline comments on GitHub. No Dam Secure account is needed. The triage is recorded against the GitHub account that replied, and the pull request's check updates to match.
Commands
Reply to a Dam Secure inline comment with one of:
| Reply | Result |
|---|---|
/fixed | Marks the sub-issue Fixed |
/ack | Marks the sub-issue Confirmed |
/dismiss [reason] | Dismisses the sub-issue, with an optional reason |
Dismissals work the same way as in the app, and are remembered across rescans. If a command can't be applied, Dam Secure replies with the reason.
Enable it
An organisation admin can turn it on or off in Settings → Repos → Triage from PR replies. It needs:
- Post PR comments with findings turned on.
- A Comment format that includes inline comments.
- If Block PRs with findings is on, Minimum severity for inline comments at or below the Blocking severity, so every blocking issue has a comment to reply to.
Settings lists these under the toggle and shows any changes needed before saving.
Limits
- Inline comments are posted for up to 20 sub-issues per pull request, on lines in the diff. Triage the rest in the Dam Secure app.
- Edited replies are not reprocessed.