Change Details

From the thread that I started in #engineering-all: > Briefly: No triggers are matching files in the project root and so patches to those files are never tagged as verified. The project's access rights stop someone from manually V+1'ing the patch too so it can't be manually submitted For example, see https://gerrit.wikimedia.org/r/c/mediawiki/libs/metrics-platform/+/879164, which can't be V+1'ed or V+2'ed manually.

From the thread that I started in #engineering-all: > Briefly: No triggers are matching files in the project root and so patches to those files are never tagged as verified. The project's access rights stop someone from manually V+1'ing the patch too so it can't be manually submitted == Actual Behavior For example, see https://gerrit.wikimedia.org/r/c/mediawiki/libs/metrics-platform/+/879164, which can't be V+1'ed or V+2'ed manually. == Expected Behavior I can manually V+1 or V+2 the patch.

From the thread that I started in #engineering-all: > Briefly: No triggers are matching files in the project root and so patches to those files are never tagged as verified. The project's access rights stop someone from manually V+1'ing the patch too so it can't be manually submitted == Actual Behavior For example, see https://gerrit.wikimedia.org/r/c/mediawiki/libs/metrics-platform/+/879164, which can't be V+1'ed or V+2'ed manually. == Expected Behavior I can manually V+1 or V+2 the patch.