Import/Merge supabase configs?

[AnmAtAnm]

Does supabase support a means to import all the components of another supabase project/repo?

For example, say I have built a project with a set of features to cover a self contained, common use case. It probably includes some migrations, functions, routes. They are general enough to be reused, either internally or by others (open source). I check that in. But I'm also interested in building a more niche or private set of functionally on top of that, and because of data size/locality, it is best to build them into the same deployed project and database.

Is there a way to indicate a another supabase repo (or project in an adjacent directory) is a dependent, so all the files/definitions from that supabase config get merged? That is, the other migrations/functions/routes/etc are included in the referring supabase before deployment?

Ideally, such a solution should:

• Not leave orphan files when deleted/renamed in other repo.
• not pollute the git change status of local repo
• Merge contents of select config files at runtime without actually changing contents of local config file
• build/deploy as one instance