How it works

You send the change. You get back whether it fits.

Send it after you already have a change.

1. 01

   Send the change and the files

   The call carries an instruction (what the change was supposed to do), the proposed change, and the current files. Caps reject at 16 files and 96 KiB total. They do not truncate.

2. 02

   We try it against your files

   Each hunk is matched against the files you sent. A hunk applies when its old-side window occurs once. Several matches, or a malformed change, stop that hunk.

3. 03

   You get whether it fits

   The response names applied, apply_class, and the files it touched.