Replace Travis with Actions

Author: Zac-HD

.github/workflows/main.yml

@@ -132,4 +132,6 @@ jobs:
       with:
         python-version: ${{ matrix.python-version }}
     - name: Deploy package
+      env:
+        TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
       run: TASK=${{ matrix.task }} ./build.sh

CONTRIBUTING.rst

@@ -152,12 +152,13 @@ unless you want to make changes to the test config. You also mostly don't need t
 except to type ``./build.sh`` followed by the name of the task you want to run.
 
 All of it will be checked on CI so you don't *have* to run anything locally, but you might
-find it useful to do so: A full Travis run takes about twenty minutes, and there's often a queue,
+find it useful to do so: A full CI run can take up to twenty minutes,
 so running a smaller set of tests locally can be helpful.
 
 The build system should be "fairly" portable, but is currently only known to work on Linux or OS X. It *might* work
-on a BSD or on Windows with cygwin installed, but it hasn't been tried. If you try it and find it doesn't
-work, please do submit patches to fix that.
+on a BSD or on Windows with cygwin installed, but it hasn't been tried.  Windows with WSL does work,
+as for Linux, and since OS-specific issues are rare for Hypothesis that's pretty useful.
+If you try it and find it doesn't work, please do submit patches to fix that.
 
 Some notable commands:
 

hypothesis-python/tests/README.rst

@@ -12,8 +12,8 @@ library tests itself!
 The very short version
 ======================
 
-- To improve code coverage (eg because ``make check-coverage`` / the Travis
-  build is failing), go to ``cover/``
+- To improve code coverage (eg because ``make check-coverage`` or CI is failing),
+  go to ``cover/``
 - For longer / system / integration tests, look in ``nocover/``
 - For tests that require an optional dependency, look in the directory
   named for that dependency.
@@ -34,7 +34,7 @@ Some scenarios
     in ``test_direct_strategies.py``.  Strategies with optional dependencies
     should go in ``hypothesis.extras``, and the tests in their own module
     (ie not in ``cover``).  When you think you might be done, push and let
-    Travis point out any failing tests or non-covered code!
+    our CI system point out any failing tests or non-covered code!
 
 **I've made some internal changes**
     That's not very specific - you should probably refer to the test-finding
@@ -68,6 +68,9 @@ Still here?  Here's a note on what to expect in each directory.
     features such as ``mark.parametrize``, ``mark.skipif``, and ``raises``
     for other functions that are often useful when writing tests.
 
+``conjecture/``
+    As for ``cover/``, but specific to ``hypothesis.internal.conjecture``.
+
 ``cover/``
     The home of enough tests to get 100% branch coverage, as quickly as possible
     without compromising on test power.  This can be an intimidating target,

hypothesis-python/tests/conftest.py

@@ -54,7 +54,7 @@ def consistently_increment_time(monkeypatch):
     """Rather than rely on real system time we monkey patch time.time so that
     it passes at a consistent rate between calls.
 
-    The reason for this is that when these tests run on travis, performance is
+    The reason for this is that when these tests run in CI, their performance is
     extremely variable and the VM the tests are on might go to sleep for a bit,
     introducing arbitrary delays. This can cause a number of tests to fail
     flakily.

secrets.tar.enc

@@ -97,7 +97,7 @@ def git(*args):
     subprocess.check_call(("git",) + args)
 
 
-TOOLING_COMMITER_NAME = "Travis CI on behalf of David R. MacIver"
+TOOLING_COMMITER_NAME = "CI on behalf of the Hypothesis team"
 
 
 def configure_git():
@@ -128,11 +128,6 @@ def push_tag(tagname):
 
 def assert_can_release():
     assert not IS_PULL_REQUEST, "Cannot release from pull requests"
-    assert has_travis_secrets(), "Cannot release without travis secure vars"
-
-
-def has_travis_secrets():
-    return os.environ.get("TRAVIS_SECURE_ENV_VARS", None) == "true"
 
 
 def modified_files():
@@ -220,15 +215,7 @@ def decrypt_secrets():
     os.chmod(DEPLOY_KEY, int("0600", 8))
 
 
-IS_TRAVIS_PULL_REQUEST = os.environ.get("TRAVIS_EVENT_TYPE") == "pull_request"
-
-IS_CIRCLE_PULL_REQUEST = (
-    os.environ.get("CIRCLE_BRANCH") == "master"
-    and os.environ.get("CI_PULL_REQUESTS", "") != ""
-)
-
-
-IS_PULL_REQUEST = IS_TRAVIS_PULL_REQUEST or IS_CIRCLE_PULL_REQUEST
+IS_PULL_REQUEST = os.environ.get("GITHUB_REF", "").startswith("refs/pull/")
 
 
 def all_projects():

tooling/src/hypothesistooling/__init__.py

@@ -120,12 +120,10 @@ def deploy():
         print("Not deploying due to not being on master")
         sys.exit(0)
 
-    if not tools.has_travis_secrets():
+    if "PYPI_TOKEN" not in os.environ:
         print("Running without access to secure variables, so no deployment")
         sys.exit(0)
 
-    print("Decrypting secrets")
-    tools.decrypt_secrets()
     tools.configure_git()
 
     for project in tools.all_projects():

tooling/src/hypothesistooling/__main__.py

@@ -100,7 +100,7 @@ def upload_distribution():
     tools.assert_can_release()
 
     # Yes, cargo really will only look in this file. Yes this is terrible.
-    # This only runs on Travis, so we may be assumed to own it, but still.
+    # This only runs in CI, so we may be assumed to own it, but still.
     unlink_if_present(CARGO_CREDENTIALS)
 
     # symlink so that the actual secret credentials can't be leaked via the

tooling/src/hypothesistooling/projects/conjecturerust.py

@@ -181,8 +181,7 @@ def upload_distribution():
             "twine",
             "upload",
             "--skip-existing",
-            "--config-file",
-            tools.PYPIRC,
+            "--username=__token__",
             os.path.join(DIST, "*"),
         ]
     )
@@ -210,8 +209,6 @@ def upload_distribution():
             "body": changelog_body,
         },
         timeout=120,  # seconds
-        # Scoped personal access token, stored in Travis environ variable
-        auth=("Zac-HD", os.environ["Zac_release_token"]),
     ).raise_for_status()