Translations:Continuous integration/Allow list/2/en

Not being on the list means that unit test failures or code style issues only get caught when a trusted user tries to test or merge the patch, so the patch author's time is wasted on waiting for an extra code review cycle even though the issues with their patch could be easily detected by a machine without causing delay. (To some extent this can be mitigated by running the tests locally but that's not always easy to do.) Being on the list does not require a high level of trust - just that they're not malicious. If you are preparing for a development-focused event such as a hackathon, please add participants beforehand. The allow list is in $git - just add the user's primary Gerrit e-mail address to the list (in escaped format). An example patchset doing that is $patch.