# Keeping Version history of bitrise.yml

**URL:** <https://discuss.bitrise.io/t/keeping-version-history-of-bitrise-yml/7276>\
**Category:** Question & Answer\
**Created:** [December 6, 2018, 2:37pm UTC](https://discuss.bitrise.io/t/keeping-version-history-of-bitrise-yml/7276 "2018-12-06T14:37:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![spinach](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/spinach/32/1258_2.png) [@spinach](https://discuss.bitrise.io/u/spinach)\
**Post date:** [December 6, 2018, 2:37pm UTC](https://discuss.bitrise.io/t/keeping-version-history-of-bitrise-yml/7276/1 "2018-12-06T14:37:29Z")

</div>

Hello 👋

I hope all is well, and thanks for the nice service you’re offering!

I’m curious about the following: Let’s say sometime in the future, someone accidentally deletes some workflow. I guess it will be hard to do a rollback and recover the workflow, is that correct?

Which leads me to the second question: is there a way to keep doing all changes through the web dashboard, while commiting the `bitrise.yml` file to the source repo when changes are made? I know that there is a way to manually download the file from the web dashboard, but I’m wondering if there is a way to access the `bitrise.yml` file programmatically somehow, and commit it to the repo?

By the way, I read the guide on [using bitrise.yml from repository](https://devcenter.bitrise.io/tips-and-tricks/use-bitrise-yml-from-repository/) but couldn’t see anything related to being able to use the web dashboard to do all changes while keeping a version history of the `bitrise.yml` in case we need to go back to a specific version (also to keep a backup somewhere).

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [December 7, 2018, 3:37pm UTC](https://discuss.bitrise.io/t/keeping-version-history-of-bitrise-yml/7276/2 "2018-12-07T15:37:02Z")

</div>

Hi @spinach, thanks for your question and the nice words! 😊

While there isn’t complete history of .ymls available on the UI, you can restory any state of the .yml based on earlier workflows: [https://blog.bitrise.io/restore-current-bitrise-yml-to-a-builds-bitrise-yml](https://blog.bitrise.io/restore-current-bitrise-yml-to-a-builds-bitrise-yml)

As for storing the .yml in the repo, I’d recommend you check out our guide on our Offline Workflow Editor: [https://devcenter.bitrise.io/bitrise-cli/offline-workflow-editor/](https://devcenter.bitrise.io/bitrise-cli/offline-workflow-editor/)

The workflow from the .yml can be run by `cd`-ing into the directory where the .yml is present, and after that (in the same script step) calling the `bitrise run <workflowname>` command.

Hope this helps clear things up, let us know if you have any questions! 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [January 6, 2019, 3:37pm UTC](https://discuss.bitrise.io/t/keeping-version-history-of-bitrise-yml/7276/3 "2019-01-06T15:37:05Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.