Vet Gerrit Client

Vet allows to review code on Gerrit using a pull-request workflow similar to GitHub, GitLab, Bitbucket and others.

No more commit amend Gerrit can't manage more than one commit per change set. Because of that, the widespread and cumbersome workflow is to have a single local commit and amend it every time you want to update the changeset.

Using Vet, Gerrit keeps seeing one commit per change set while you don't have to rewrite your history anymore. Each time you will ask to push to Gerrit, Vet will forge and push a single commit based on your source branch commit sequence.

Now you can have feature branches With Vet, you can have feature branches. If you set the correct Gerrit authorizations, you can push them as standard branches. Vet is able to manage git remote pushed or local only source branches the same way.

Checkout the feature branch to test or hack the changeset As a reviewer you want to test the change set locally? Just checkout the feature branch.

Now maybe you want to contribute to the change set? Run Vet push and your changes are added to the correct change set.

No pre commit hook needed Vet computes the Gerrit change id on the fly before pushing to Gerrit. Say bye to the pre-commit script.

No Gerrit REST or SSH api involved Git is the only channel used by Vet to communicate with Gerrit. Vet doesn't need to know your credentials.

Use any git remote protocol Because Vet delegates all Gerrit communication to git, your remote access protocol is only limited by git:

file ssh http(s) ...