Putting it in general git admin triage queue and CCing this week's git admin.

Also, I don't think it is possible to always copy all scores.

For the reference, here's current config (https://chromium.googlesource.com/angle/+/refs/meta/config/project.config):

[label "Code-Review"]
	copyMinScore = true
	copyMaxScore = true
	copyAllScoresOnTrivialRebase = true
	copyAllScoresIfNoCodeChange = true

And here's possible set of knobs there (https://gerrit-review.googlesource.com/Documentation/config-labels.html):

label.Label-Name.copyMinScore
label.Label-Name.copyMaxScore
label.Label-Name.copyAllScoresOnMergeCommitFirstParentUpdate
label.Label-Name.copyAllScoresOnTrivialRebase
label.Label-Name.copyAllScoresIfNoCodeChange
label.Label-Name.copyAllScoresIfNoChange

There's no option to "copyAllScoresAlways".

Any at Google who maintains Gerrit? I'm wary of leaving this bug without an owner, I have a feeling it'll sit in vacant space until the end of time.

Infra>Git>Admin is a bug queue that is actively triaged (we have a weekly bug triage rotations and stuff). I have faith in the system :)

Hmm well *I* have no idea.  If this isn't supported at the moment it sounds like it should be a feature request in https://bugs.chromium.org/p/gerrit/issues/list?

This is indeed possible. An example configuration:
[label "Code-Review"]
        abbreviation = R
        value = -1 Don't submit as-is
        value =  0 No score
        value = +1 Looks good to me
        defaultValue = 0
        function = MaxWithBlock
        copyMinScore = true
        copyMaxScore = true
        copyAllScoresOnTrivialRebase = true
        copyAllScoresIfNoCodeChange = true

Barring the min/max labels, this should let LGTM be “sticky”.

This would mean there is no Code-Review +2 though, I think. We would like to keep +1 and +2, but make the +1s sticky.

You don’t have to change the range of review values. It will still remain sticky.

Keep in mind there is a bug with sticky LGTMs that is being fixed: https://bugs.chromium.org/p/gerrit/issues/detail?id=4373

Oh, cool. How can we get the config then that you listed above? Then after the gerrit bug is fixed we'll be good to go?

Hm... It looks like the configuration is already set up that way (from https://chromium.googlesource.com/angle/+/refs/meta/config/project.config):

[label "Code-Review"]
	function = MaxWithBlock
	abbreviation = R
	copyMinScore = true
	copyMaxScore = true
	copyAllScoresOnTrivialRebase = true
	copyAllScoresIfNoCodeChange = true
	value = -2 Do not submit
	value = -1 I would prefer that you didn't submit this
	value =  0 No score
	value = +1 Looks good to me, but someone else must approve
	value = +2 Looks good to me, approved
	defaultValue = 0

Is this still an issue for folks, or did the bug mentioned in #8 actually fix this?

Second ping :). If there's no response for another day I'll close.

Did the Gerrit change land? I'd like to test it, but unsure if it's on the deployed Gerrit site for ANGLE.

Ah... I saw that it was committed. I'll check to make sure that it's deployed

Yes, this is deployed for angle: https://chromium.googlesource.com/angle/angle

Can angle confirm whether their code-review labels are sticky now or not?

I can confirm this does not work as intended currently, Code-Review +1 labels are dropped. Smut, can you close this as WontFix if there is no possible resolution?

See: https://chromium-review.googlesource.com/#/c/374338/

I posted on https://bugs.chromium.org/p/gerrit/issues/detail?id=4373 that their fix doesn't seem to have worked.

They tell me it's working as intended not to copy Code-Review+1. They only copy +2 because +1 means someone else must approve anyways. +1 only sticks across rebases and commit message changes.

Thanks. If I wanted to file a feature request for our use case, do you know which issue tracker or labels to use?

I think you could use https://bugs.chromium.org/p/gerrit/issues/entry?template=Feature%20Request.