diff --git a/README.md b/README.md
index d88f8e6..0e38bda 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,7 @@ and pairing with smart people at Hashrocket.
 
 For a steady stream of TILs, [sign up for my newsletter](https://tinyletter.com/jbranchaud).
 
-_963 TILs and counting..._
+_964 TILs and counting..._
 
 ---
 
@@ -945,6 +945,7 @@ _963 TILs and counting..._
 ### Vercel
 
 - [Add Web Server Layer Redirects](vercel/add-web-server-layer-redirects.md)
+- [Deploy An App Without Pushing An Empty Commit](vercel/deploy-an-app-without-pushing-an-empty-commit.md)
 - [Naming Of The Vercel Config File](vercel/naming-of-the-vercel-config-file.md)
 - [Share Development Environment Variables Via CLI](vercel/share-development-environment-variables-via-cli.md)
 
diff --git a/vercel/deploy-an-app-without-pushing-an-empty-commit.md b/vercel/deploy-an-app-without-pushing-an-empty-commit.md
new file mode 100644
index 0000000..8aa5819
--- /dev/null
+++ b/vercel/deploy-an-app-without-pushing-an-empty-commit.md
@@ -0,0 +1,23 @@
+# Deploy An App Without Pushing An Empty Commit
+
+The [Vercel CLI](https://vercel.com/docs/cli) allows you to make updated
+deployments of an app right from the command line. Many providers require you
+to push a new commit to the main branch to trigger a deployment. If there are
+changes, you can trigger a deployment by pushing these. If there aren't
+changes, but you want to re-deploy what is already there, then you have to
+create an empty commit and push that.
+
+With the [Vercel CLI](https://vercel.com/docs/platform/deployments#vercel-cli),
+you can deploy and re-deploy the app without pushing commits.
+
+To trigger a preview deployment:
+
+```bash
+$ vercel
+```
+
+To trigger a production deployment:
+
+```bash
+$ vercel --prod
+```