Change Details

I think, to improve developer experience (especially for the new), it's important that a patch is not posted on gerrit before some checks are locally done. These checks would catch errors (formatting, lint, syntax etc) would otherwise fail CI tests on Gerrit and prolong the code review process. This could be achieved by using a git hook to run a shell script with command that can be run on ones local development environment.

I think, to improve developer experience (especially for the new), it's important that a patch is not posted on gerrit before some checks are locally done. These checks would catch errors (formatting, lint, syntax etc) that would otherwise fail CI tests on Gerrit and eventually prolong the code review process. This could be achieved by using a git hook to run a shell script with command that can be run on ones local development environment.

I think, to improve developer experience (especially for the new), it's important that a patch is not posted on gerrit before some checks are locally done. These checks would catch errors (formatting, lint, syntax etc) that would otherwise fail CI tests on Gerrit and eventually prolong the code review process. This could be achieved by using a git hook to run a shell script with command that can be run on ones local development environment.