You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.
That's something I'll be putting in place soon, we'll just have a development branch and master, and start using the git flow methodology. So, create a branch, merge to development, and if testing is good, we'll merge to master.
Regarding the database changes, I think that looks good. Definitely something we should all sit down and discuss more shortly. I apologize for my lack of updates lately, we are settling on our new house this week, and we've just been swamped with the moving process, so, hopefully in about two weeks I can get things back to normal and start development back up.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I thought I'd start a thread regarding the needed modifications to the database schema. Hopefully we can consolidate the discussion to this issue.
@brianwarehime It would be helpful to create a new branch where we could commit code changes that effect the database without disrupting the master.
The text was updated successfully, but these errors were encountered: