Add migrations to version control

[wkyoshida]

Terms

• [X] I have searched open and closed issues
• [X] I agree to follow activist's Code of Conduct

Issue

This issue is to start saving the needed migrations to the database in version control.

We can use the issue to discuss:

• When to actually start
  • Likely once we deem the backend to be in a "ready-enough" state
• When and how to generate future migration files based on new changes to the backend
  • Included in PRs? After a PR is merged?

cc: @andrewtavis, @to-sta

[Mitadru17]

sir I would like to work on this issue. Please assign me this issue.

[Zangaleua]

Hey! Is it possible to get this assigned? Im looking for projects to help with using python!

[andrewtavis]

Hey @Zangaleua 👋 I think it might be best if we wait on this one for now, but let's check 😊 @to-sta, do you think we can do this at this point? Wouldn't be final, but so long as they're in there and we have the process of updating them documented?

[to-sta]

@andrewtavis I would say we wait till we hit production and keep the migration files up to date with production.

I would say we either close this issue or block it for now.

[Zangaleua]

@andrewtavis since this issue is closed for now, could you point me in the direction of a case that needs help?

sorry to be a bother, kinda new to github!

[andrewtavis]

No need to apologize whatsoever, @Zangaleua! We were all new at some point :) If you're interested in frontend, then maybe you could take a look at #894? We can also make other suggestions if you'd prefer to look into something else :)