| commit | 2a562ac1b074793625564c5b01390d9f81cfd9c6 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Aug 07 08:57:09 2025 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Aug 07 14:16:54 2025 -0700 |
| tree | 0a36da089d32e56581c8a43f144757bbd954ed25 | |
| parent | 3226f14a5393273396c3d78f153ca03c1b393cab [diff] |
Consider the current logged-in user for active users tracking Before this change, the user tracked for freshening the set of active users was the one checked for group ownership, which may or may not be the user actively using Gerrit. A user admin scanning the permissions of all users could therefore trigger implicitly the including of all accounts as active, which would not be the case. Fetch the current thread active user and use that account id for tracking the activity, rather than the account passed as paramemter for membership check. Change-Id: Id38e0bb5fd6f41effde9c76055c2f1daeab3a983
This repository contains a collection of Gerrit scripting plugins that are intended to provide simple and useful extensions.
Gerrit needs to be able to recognise the scripts syntax and being able to load them as plugins.
In order to be able to run Groovy scripts, you need to install first the Groovy scripting provider and then copy the Groovy scripts under your Gerrit /plugins directory.
Similarly for Scala scripts, you need to install the Scala scripting provider and then copy the Scala scripts under your Gerrit /plugins directory.