diff --git a/README.md b/README.md
index c08fd5e9..fec74a7a 100644
--- a/README.md
+++ b/README.md
@@ -131,7 +131,6 @@ Whereas `tomo setup` is typically run once, you can use `tomo deploy` every time
 [→ Here is the default list of tasks invoked by the deploy command.](https://tomo-deploy.com/configuration#deployblock)<br>
 [→ The `tomo deploy` section of the reference docs explains supported command-line options, like `--dry-run`.](https://tomo-deploy.com/commands/deploy/)
 
-
 ### `tomo run [TASK]`
 
 Tomo can also `run` individual remote tasks on demand. You can use the `tasks` command to see the list of tasks tomo knows about.
@@ -146,8 +145,6 @@ One of the built-in Rails tasks is `rails:console`, which brings up a fully-inte
 
 [→ The `tomo run` section of the reference docs explains supported command-line options and has more examples.](https://tomo-deploy.com/commands/run/)
 
-
-
 ## Extending tomo
 
 Tomo has a powerful plugin system that lets you extend tomo by installing Ruby gems (e.g. [tomo-plugin-sidekiq](https://github.com/mattbrictson/tomo-plugin-sidekiq)). You can also define plugins on the fly within your project by adding simple `.rb` files to `.tomo/plugins/`. These plugins can define tasks as plain ruby methods. For example:
@@ -182,6 +179,10 @@ And run it!
 - [Writing Custom Tasks](https://tomo-deploy.com/tutorials/writing-custom-tasks/)
 - [Publishing a Plugin](https://tomo-deploy.com/tutorials/publishing-a-plugin/)
 
+## Blog posts
+
+- [Automate Rails deployments with GitHub Actions](https://mattbrictson.com/blog/deploy-rails-with-github-actions)
+
 ## Reference documentation
 
 - [Configuration](https://tomo-deploy.com/configuration/)