# Database migrations and git flow

**URL:** <https://meta.discourse.org/t/database-migrations-and-git-flow/81114>\
**Category:** Development\
**Created:** [February 21, 2018, 5:41am UTC](https://meta.discourse.org/t/database-migrations-and-git-flow/81114 "2018-02-21T05:41:32Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [February 21, 2018, 3:11pm UTC](https://meta.discourse.org/t/database-migrations-and-git-flow/81114/6 "2018-02-21T15:11:54Z")

</div>

Migrations refers to changes in the database structure. You’re not talking about pushing source code changes, which is what git is for.

Changing mail templates, and key much everything else not involving a custom plugin is done via the web interface and can’t really hurt anything, so it’s not the kind of thing that many people feel the need to do on a staging server.

If you were to develop a custom plugin that needed testing you’d host it in github and test it on a development or staging server and then rebuild to pull in the new code from git.

It sounds like you’re not planning to do that.

---

_[View the full topic](https://meta.discourse.org/t/database-migrations-and-git-flow/81114)._