I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. Should Gera unlock a finished, approved code change so it can go live? It stops our preview test environments from quietly running old code instead of the newest. Unlocking ships it now; leaving it locked means it keeps waiting, because this session is not allowed to unlock it.
The full question, as raised

Pull request 23037 is finished, reviewed and approved, but deliberately locked so only a person can release it. The change makes each preview deploy lane move its own pointer to the code it just built, so a preview stops serving a stale build. Its content review passed, every required check is green, and nothing is outstanding on it. The lock is a label this session is instructed never to remove itself, so it cannot merge until Gera releases it or tells the session to.

Why, and what was tried
The session raising this recommends: Unlock it — let it merge now
The review already passed and every required check is green, so the only thing between this and done is the label; a comparable pull request sat releasable for seven days earlier and was then closed with the work thrown away and redone.
Tried first, unsuccessfully: Asked the decider whether to raise this at all or simply record that it waits on a person. It ruled twice, with the options reversed, that raising is right: a note in this session's own history surfaces nowhere, and the automatic six-hour sweep that finds releasable pull requests can never list this one, because a lock a person applied reads as undecided by design and so never enters that sweep's ready list.

1b2bcc95 is parked on this.

Answered and withdrawn (1)
Pick an option above, then press Done.
PropFlow Docs