Description of the problem / feature request:

The presence of a .bazelversion file that defines any non-matching version at the root of a directory structure prevents bazel from intepreting any commands in any subdirectory, including bazel version, help, info.

However, these are the commands needed to debug why .bazelversion is not satisfied, or to query non-build-related hel

Currently, when entering epic mode the README is frozen in the last level of the tower. When you're trying to fine-tune the score for a level other than the last one, it would be helpful if we had the README for that level available. The proposal is that when entering epic mode, the README is updated with all levels, one following the other.

Example:

# Starbolt - beginner

无法通过package启动app

• Google Pixel XL
• uiautomator2的版本号:2.9.6
• 代码:

`
d.app_start('com.appatomic.vpnhub')

Traceback (most recent call last):
File "", line 1, in
File "/workspace/venv/lib/python3.6/site-packages/uiautomator2/init.py", line 1316, in app_start
info = self.app_info(package_name)
File "/workspace/venv/lib/python3.6/site-packages/uiautomator2/

We currently have Gen.forAll { it == true }. If we want to invert it, it's ok to write Gen.forAll { !(it == true) } .

It would be syntactically pleasant to write Gen.forNone instead, like:

test("Random string shouldn't be a valid email") {
     Arb.string().forNone { it.isEmail() }` 
}

vs

test("Random string shouldn't be a valid email") {
    Arb.string().forAll

The issue is based on the discussion in #559.

@zvirja

should we probably modify CI so that doc is published automatically on push to master? This way if we don't want doc to be released right now - just keep it in a branch. Otherwise, we have this non-synchronized docs and manual work.. 😟

@dtchepak

I'm not sure what to do about publishing docs. It would be nice to auto-publish,