Note though that it's unlikely that the

github_source

dbt model will work with the

tap-github

extractor without some (many?) changes, since it was built specifically for the schema output by Fivetran's GitHub extractor(+loader), not

tap-github

Also note that as part of

meltano elt

,

dbt run

will automatically be invoked with arguments (profile, models, etc) determined by config settings listed here: https://gitlab.com/meltano/meltano/blob/master/src/meltano/core/bundle/discovery.yml#L710 As mentioned under https://meltano.com/docs/command-line-interface.html#pipeline-environment-variables, the value of

models

(which models to run, in your case:

github_source

, or the name of your

tap-github

-compatible fork) is determined automatically based on the value of that setting, which by default has the value

$MELTANO_EXTRACTOR_NAMESPACE my_meltano_model

, which expands to

tap_github my_meltano_model

when the

tap-github

extractor is used. ``my_meltano_project`` refers to models defined project-locally in your

transform/models/my_meltano_project

directory.

In your case, you'll want to override it specifically on a per-pipeline basis using the

DBT_MODELS

environment variable:

DBT_MODELS=github_source meltano elt ...

, or you can override the setting for all pipeline runs in

meltano.yml

:

meltano config dbt set models github_source

@nehil_jain Let me know if that helps! This all deserves to be much better documented, and going through this with you will help me figure out where the gaps in the docs are, and what isn't as obvious or flexible as it could be 🙂