contentCreationBlocked property

bool contentCreationBlocked
getter/setter pair

While true, issue and comment writes are refused with a content-creation block, and everything else is served.

That is the shape GitHub was measured to give a block (woneprpc126): reads and git-data writes went through while one was in force. canned cannot model it, since it answers the next request whatever it is, and a block that refused the read before a write would test a block GitHub does not impose.

Implementation

bool contentCreationBlocked = false;