# How to replicate workflows between apps

**URL:** <https://discuss.bitrise.io/t/how-to-replicate-workflows-between-apps/331>\
**Category:** Question & Answer\
**Created:** [January 18, 2017, 7:34am UTC](https://discuss.bitrise.io/t/how-to-replicate-workflows-between-apps/331 "2017-01-18T07:34:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [January 23, 2017, 11:40am UTC](https://discuss.bitrise.io/t/how-to-replicate-workflows-between-apps/331/6 "2017-01-23T11:40:45Z")

</div>

> [@freever](#):
>
> If I add an extra git clone step to clone the repo with the bitrise.yml file in it

Please don’t do that, use a **Script** step instead and `git clone` the config repo there. More info about why **you should not use the `Git Clone` step for any other repo, only for the main one** can be found at: [Can a bitrise "build" be triggered from more than one repository? - #4 by viktorbenei](http://discuss.bitrise.io/t/can-a-bitrise-build-be-triggered-from-more-than-one-repository/349/4) - or, alternatively, add the second repo as a **submodule** to the main repo, that will be handled automatically by the **Git Clone** step.

Other than that, the same thing applies for this solution what’s described at [Managing an app's bitrise.yml file - Bitrise Docs](http://devcenter.bitrise.io/tips-and-tricks/use-bitrise-yml-from-repository/)

> Define a “wrapper” build config on [bitrise.io](http://bitrise.io), which defines how and from where your bitrise.yml will be retrieved.

So, it doesn’t matter where you store the “build config `bitrise.yml`”, you can store it anywhere, just make sure that it’s downloaded/available before you’d run `bitrise run "${BITRISE_TRIGGERED_WORKFLOW_ID}"` on it.

One more thing, the simple `bitrise run "${BITRISE_TRIGGERED_WORKFLOW_ID}"` call only only works if you download/make the `bitrise.yml` available **at the root** of the repository (technically it have to be at the “current working directory”, which is by default the root of the repository, but can be changed with e.g. the **Change Working Directory …** step). You’re of course free to download it anywhere else, in that case you just have to specify where it’s located with the `--config` flag:

```auto
bitrise run --config /path/to/bitrise.yml "${BITRISE_TRIGGERED_WORKFLOW_ID}"

```

---

_[View the full topic](https://discuss.bitrise.io/t/how-to-replicate-workflows-between-apps/331)._