tree acb048e4cdca5b0475324e0f21d4db7acc805125
parent b5bea5a554d71db70543b90ba6a74d91c567e193
author Patrick Hiesel <hiesel@google.com> 1515751731 +0100
committer Patrick Hiesel <hiesel@google.com> 1515751856 +0000

Make project state check in FORCE_UPDATE explicit

The majority of code in {Project,Ref,Change}Control is now about
permissions, but not all. Exceptions include checks for a project's
state. This is confusing, because users are presented with an exception
telling them that they lack some kind of permission while the real
reason for the failed operation is that the project's current state
doesn't permit the operation.

This is part of a series of commits to remove all project state checks
from *Control classes and make explicit checks instead.

Change-Id: Ic497f0bbd6c0c128d3df81be34c382bba1a0d1b0