You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/multi_repo.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,6 +184,14 @@ gateways:
184
184
185
185
Even if you do not have a need for multiple repos now, consider adding a `project` key so that you can easily support multiple repos in the future.
186
186
187
+
## Running migrations with multiple repositories
188
+
189
+
When doing a [migration](./migrations.md), pass in a single repo path using the `-p` flag. It doesn't matter which repo you choose.
190
+
191
+
```
192
+
$ sqlmesh -p examples/multi/repo_1 migrate
193
+
```
194
+
187
195
## Multi-Repo dbt projects
188
196
189
197
SQLMesh also supports multiple repos for dbt projects, allowing it to correctly detect changes and orchestrate backfills even when changes span multiple dbt projects.
0 commit comments