Willy Tarreau 351c7e6598 DEV: patchbot: don't pretend a save succeeded when the server ignored it ... The save handler treated any HTTP 200 as a full success and advanced the local reference for everything it had sent, only special-casing the reported conflicts. But the server legitimately drops directives it cannot parse, and answers "OK <n> directives applied" with what it really did. The typical case is an outdated update scripton the server which ignores the whole "setnotes" directive, applies nothing, and the client still displayed the edit as saved... until the next "Get updates" reverted it. Let's count the directives sent, and when the server's applied count plus the reported conflicts don't add up, believe the server, not ourselves: advance nothing, keep every edit local (boxes open, save button lit) and tell the user how many changes were ignored, suggesting a version mismatch.		2026-07-07 14:45:32 +02:00
..
post-ai.sh	DEV: patchbot: don't pretend a save succeeded when the server ignored it	2026-07-07 14:45:32 +02:00
process-patch-v15.sh	DEV: patchbot: produce a verdict for too long commit messages	2024-01-09 14:46:04 +01:00
submit-ai.sh	DEV: patchbot: add the AI-based bot to pre-select candidate patches to backport	2023-12-18 20:50:51 +01:00
update-3.0.sh	DEV: patchbot: pass the branch version to the generated page	2026-07-07 10:58:38 +02:00