From 0874a6aac40e3d0312037b02ec9c4c18fb129538 Mon Sep 17 00:00:00 2001
From: Maxime Delporte <maxime@civiterra.fr>
Date: Thu, 6 Nov 2025 10:17:12 +0100
Subject: [PATCH] Adding 'Remote migration files' sub-section.

---
 README.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/README.md b/README.md
index 0035a02..0a4fd5b 100644
--- a/README.md
+++ b/README.md
@@ -158,6 +158,18 @@ $ migrate -path=./migrations -database=$EXAMPLE_DSN force 1
 
 Once you force the version, the database is considered 'clean' and you should be able to run migrations again without any problem.
 
+### Remote migration files
+
+The migrate tool also supports reading migration files from remote sources including Amazon S3 and GitHub repositories. For example :
+
+```bash
+$ migrate -source="s3://<bucket>/<path" -database=$EXAMPLE_DSN up
+$ migrate -source="github://owner/repo/path#ref" -database=$EXAMPLE_DSN up
+$ migrate -source="github://user:personal-access-token@owner/repo/path#ref" -database=$EXAMPLE_DSN up
+```
+
+More information about this functionality and a full list of the supported remote resources can be [found here](https://github.com/golang-migrate/migrate#migration-sources).
+
 ## Additional Information
 
 ### How different Go Types are encoded