diff --git a/.github/workflows/run_tests.yml b/.github/workflows/run_tests.yml
new file mode 100644
index 0000000..241bd64
--- /dev/null
+++ b/.github/workflows/run_tests.yml
@@ -0,0 +1,57 @@
+# Based on https://jacobian.org/til/github-actions-poetry/
+# Run this job on pushes to `main`, and for pull requests. If you don't specify
+# `branches: [main], then this actions runs _twice_ on pull requests, which is
+# annoying.
+
+on:
+    push:
+      branches: [main]
+    pull_request:
+  
+  jobs:
+    test:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+  
+        # If you wanted to use multiple Python versions, you'd have specify a matrix in the job and
+        # reference the matrixe python version here.
+        - uses: actions/setup-python@v2
+          with:
+            python-version: 3.9
+  
+        # Cache the installation of Poetry itself, e.g. the next step. This prevents the workflow
+        # from installing Poetry every time, which can be slow. Note the use of the Poetry version
+        # number in the cache key, and the "-0" suffix: this allows you to invalidate the cache
+        # manually if/when you want to upgrade Poetry, or if something goes wrong. This could be
+        # mildly cleaner by using an environment variable, but I don't really care.
+        - name: cache poetry install
+          uses: actions/cache@v2
+          with:
+            path: ~/.local
+            key: poetry-1.1.12-0
+  
+        # Install Poetry. You could do this manually, or there are several actions that do this.
+        # `snok/install-poetry` seems to be minimal yet complete, and really just calls out to
+        # Poetry's default install script, which feels correct. I pin the Poetry version here
+        # because Poetry does occasionally change APIs between versions and I don't want my
+        # actions to break if it does.
+        #
+        # The key configuration value here is `virtualenvs-in-project: true`: this creates the
+        # venv as a `.venv` in your testing directory, which allows the next step to easily
+        # cache it.
+        - uses: snok/install-poetry@v1
+          with:
+            version: 1.1.12
+            virtualenvs-create: true
+            virtualenvs-in-project: true
+        
+        # Now install _your_ project. This isn't necessary for many types of projects -- particularly
+        # things like Django apps don't need this. But it's a good idea since it fully-exercises the
+        # pyproject.toml and makes that if you add things like console-scripts at some point that
+        # they'll be installed and working.
+        - run: poetry install --no-interaction --with tests
+  
+        # And finally run tests. I'm using pytest and all my pytest config is in my `pyproject.toml`
+        # so this line is super-simple. But it could be as complex as you need.
+        - run: poetry run pytest
\ No newline at end of file