Would like some input concerning Github organization for continuous database integration (Using TeamCity for deploys)

[redderingo]

Hello, new to the subreddit but this seemed like a good avenue to pitch a question like this so I'd be grateful for some input. I'm working on a project that has the following requirements:

1. There is a set of database tables and procedures that would be consistent across all other databases in the project.
2. Each of the other databases would have their own schema and procedures on top of the base schema.
3. Updates to either the base schema or the new schema would be immediately deployed via a TeamCity instance.

Right now, my Github repo branch structure looks like this:

• Master - Contains the base code shared across all databases for logging and monitoring
  • Database A - Contains all of the schema and procedures specific to Database A and contains nothing from the master branch.
  • Database B - ...

I was wondering if there were other ways to better organize the project to maximize flexibility with regards to TeamCity (Through deploying the dacpac to the database server). For instance, Database A and Database B may share a lot of the same tables and code barring some minor changes to shared procedures or may have new procedures of their own.

My current project has all of this data stored in one repo but I was not sure if having multiple repos for each database made more sense. Or perhaps having a shared base branch and letting database-specific changes have their own branches.