Repository navigation
Conversation
|
Warning Review limit reachedNext included review available in 57 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
f51e560 to
533e044
Compare
Resolved via the updated fix/stacked-merge-retargets-base (which already contains origin/main). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015rnEEjXWDBdePRhKMmZr1w
|
This change is already in Generated by Claude Code |
Summary
merge --notify(andPR_SPLIT_WEBHOOK_URL) accepted any string.urllib.request.urlopenhappily openedfile://targets — the tool then logged "Webhook notification sent to file:///…" — and a bare hostname failed only after all merges with an obscure "unknown url type" warning.The option now has a typer callback requiring an http(s) scheme with a host; anything else exits 2 with
must be an http(s) URL, got '…'before the plan is even read. The help text and README's--notifyparagraph say so, and the README now also states that a delivery failure (timeout, non-2xx) is a warning that does not change the exit code.Stacked on #160 (top of stack #99 = #67→#98→#103→#160), which owns the
mergecommand.Test plan
TestNotifyUrlValidation:file://, bare word,ftp://,https://without a host → exit 2 beforeplan_exists; env var validated; http URL passes — four of six fail on the basejavascript:and the absent-option path