tree a7ee85fdc016c2f8c6daacf4e5ddf03e4d79f14c
parent a7ad3e08042318ce474de4d585dfda59a2e49da6
author Youssef Elghareeb <ghareeb@google.com> 1625138589 +0200
committer Youssef Elghareeb <ghareeb@google.com> 1626856201 +0200

Store submit requirements for merged changes in NoteDb

Upon merging a change, we check for the changeset (list of changes) to
be merged, and add a batch update op for each change to store the
evaluated submit requirements in NoteDb.

Submit requirements are stored in the change meta ref
(refs/changes/$short-id/$id/meta) in the revision notes of the latest
patchset. The added test in ChangeIT makes sure submit requirements are
stored in the change notes when the change is submitted.

In a follow up change, we will update the 'Get change' endpoint to use
the logic added in this change:
* If the change is active, we will evaluate submit requirements (this is
how it's done now).
* If the change is merged, we will lookup the evaluated submit
requirements from NoteDb and return them to the user.

Change-Id: I2a63f725b9f96647bb438f9f546a48b0fbab4e12