Clone this repo:


  1. c705c98 Rename repository by Han-Wen Nienhuys · 4 months ago master
  2. b00f876 cmd/checker: fix vet errors by Han-Wen Nienhuys · 4 months ago
  3. 8754def cmd/fmtserver: delete obsolete file by Han-Wen Nienhuys · 4 months ago
  4. 00020c8 Add exe dir to $PATH earlier by Han-Wen Nienhuys · 4 months ago
  5. 96b72a1 build-deploy: make google-java-format.jar +x by Han-Wen Nienhuys · 4 months ago


This is a style verifier intended to be used with the Gerrit checks plugin.


  1. Install formatters:
go install
curl -o google-java-format.jar
  1. Obtain an HTTP password, and put it in testsite-auth. The format is username:secret.

  2. Register a checker

go run ./cmd/checker -auth_file=testsite-auth  --gerrit http://localhost:8080 \
  --language go --repo gerrit --register
  1. Make sure the checker is there
go run ./cmd/checker -auth_file=testsite-auth  --gerrit http://localhost:8080 \
  1. Start the server
go run ./cmd/checker -auth_file=testsite-auth  --gerrit http://localhost:8080


For simplicity of deployment, gerritfmt checker is stateless. All the necessary data is encoded in the checker UUID


  • handle file types (symlink) and deletions

  • more formatters: clang-format, typescript, jsformat, ... ?

  • isolate each formatter to run with a separate gvisor/docker container.

  • tests: the only way to test this reliably is to spin up a gerrit server, and create changes against the server.

  • Update the list of checkers periodically.


This currently runs the formatters without sandboxing. Critical bugs (heap overflow, buffer overflow) in formatters can be escalated to obtain the OAuth2 token used for authentication.

The currently supported formatters are written in Java and Go, so this should not be an issue.


This is not an official Google product