Review System

[TonyGermaneri]

Review requirements should be set at the graph properties top level.

New property

graph.properties.requiredReviewers = Number

When n > 0, any changes to the graph will require n reviewers to approve the changes.

Review user identity is tied to the authentication system. Reviews currently can come from anyone, including the author, because graph changes can happen so easily.

Reviews should be attached to a particular version, and be updatable to a new version. For example, if I review v1234, then a change is made, I should be able to retain the same review but mark it for v1235.

Reviews should be part of the graph's event stream, but should not effect graph state directly, they can effect it by side effect of the approval process, for example if the deploy hook updates the graph with a comment about deployment.