Hi @Kaniz Fatma,

​

The documentation mentions:

• Automatic archiving of the artifacts from job runs, including logs, results, manifests, and configuration.

​

When a dbt task runs, do the logs, manifests and index.html automatically go back to the attached repo?

​

Is there a way to run slim ci with the dbt task? Can we use pre-commit? It would be good to be able to inspect manifest, capture models that have changed, shallow clone them, test their transforms, and if succeed, run those to prod.​

​