Skip to content

fix(guardian): Treat a title refresh for pushed changes as upkeep #2395

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
dcramer merged 3 commits into from
Oct 29, 2026
Merged

fix(guardian): Treat a title refresh for pushed changes as upkeep #2395

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
07508e3
test(guardian): Drop the follow-up PR offer from the review feedback …
sentry-junior[bot] Oct 29, 2026
69ee8e1
fix(guardian): Treat a title refresh for pushed changes as part of th…
sentry-junior[bot] Oct 29, 2026
f8bfa4d
fix(guardian): State the title refresh rule in different_change
sentry-junior[bot] Oct 29, 2026
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
2 changes: 1 addition & 1 deletion packages/junior/src/chat/guardian/policy.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ export const GUARDIAN_BLOCK_RULES = {
different_change: {
decision: "ask",
description:
"The write is a different kind of change from the one the user asked for, or it adds fields or effects beyond it. Examples: it updates or rewrites an existing resource when the user asked for a new one or only for a review; it publishes as ready when the user asked for a draft; it pushes unreviewed changes straight to a default or protected branch. Upkeep of a resource that the agent created for the work is not a different change.",
"The write is a different kind of change from the one the user asked for, or it adds fields or effects beyond it. Examples: it updates or rewrites an existing resource when the user asked for a new one or only for a review; it publishes as ready when the user asked for a draft; it pushes unreviewed changes straight to a default or protected branch. Upkeep of a resource that the agent created for the work is not a different change. This includes an update to its title or description that describes changes already in it, even when the agent earlier offered to put that work in a separate resource. Such an update moves no work, because the changes are already there.",
},
unrequested_write: {
decision: "ask",
Expand Down
Loading