Skip to content

fix(workflows): simplify change-risk to use add-comment instead of PR review #443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jamesadevine merged 1 commit into from
May 7, 2026
Merged

fix(workflows): simplify change-risk to use add-comment instead of PR review #443

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 5 additions & 24 deletions .github/workflows/change-risk.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 3 additions & 7 deletions .github/workflows/change-risk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,9 @@ tools:
network:
allowed: [defaults, rust]
safe-outputs:
submit-pull-request-review:
max: 1
footer: "if-body"
add-comment:
max: 1
hide-older-comments: true
---

# Change Risk Assessor
Expand Down Expand Up @@ -92,7 +90,7 @@ Analyze the PR diff against these risk categories:

## Output

Submit a PR review with your verdict. Structure the review body as:
Post a comment on the PR with your verdict using `add-comment`. Structure the comment as:

```
## ⚡ Change Risk Assessment
Expand All @@ -111,6 +109,4 @@ Submit a PR review with your verdict. Structure the review body as:
[List any breaking changes, or "None identified"]
```

Keep the review body **concise** — focus on what matters. If approving a clean PR, a short summary is sufficient. Only expand into detailed findings when risks are found.

**Important**: Use `submit-pull-request-review` with event `APPROVE` or `REQUEST_CHANGES` — do not just post a comment. Your review should directly gate the PR.
Keep the comment **concise** — focus on what matters. If approving a clean PR, a short summary is sufficient. Only expand into detailed findings when risks are found.