Unlike `git cl presubmit` which has an API with the repo (PRESUBMIT.py files), `git cl format` is implemented by adding chromium/src-specific things into git_cl.py (and depot_tools).

It was proposed in https://chromium-review.googlesource.com/c/437919/ that something like a FORMAT.py could exist, and `git cl format` would know how to process those FORMAT.py files in the repo. Then repo-specific formatting code could be contained and versioned with the repo.

Ideally this protocol can be VERY VERY SIMPLE (like: invoke each FORMAT.py from the file path to the root of the repo. If it returns 0, it formatted the file. If it returns 1, it doesn't know how to process the file).

If this is agreeable to folks, I'd like it if we can implement this before we add too many more things to `git cl format`.
 

Unlike `git cl presubmit` which has an API with the repo (PRESUBMIT.py files), `git cl format` is implemented by adding repo-specific things into git_cl.py (and depot_tools).

It was proposed in https://chromium-review.googlesource.com/c/437919/ that something like a FORMAT.py could exist, and `git cl format` would know how to process those FORMAT.py files in the repo. Then repo-specific formatting code could be contained and versioned with the repo.

Ideally this protocol can be VERY VERY SIMPLE (like: invoke each FORMAT.py from the file path to the root of the repo. If it returns 0, it formatted the file. If it returns 1, it doesn't know how to process the file).

If this is agreeable to folks, I'd like it if we can implement this before we add too many more things to `git cl format`.