Today every new feature edits three shared files by hand
The service list, the table list and the table details all sit in shared files; 25 of 64 pull requests touched them.
Three lists name every feature, and each new feature edits them
MainDbContext.Three things are listed by hand today, at commit 9fc729e:
| What | File | Lines |
|---|---|---|
| Services | App/Modules/DomainServices.cs | all 248 |
| Tables (DbSet list) | App/StartUp/Database/MainDbContext.cs | 36 to 77 |
| Table details (indexes, links) | App/StartUp/Database/MainDbContext.cs | 89 to 341 |
| Background jobs | App/StartUp/Server.cs | 157 to 162 |
This is read from the code From code. The before and after page walks through these lines.
DomainServices.csmakes 67 service registrations, one by one, and imports 51 namespaces.MainDbContext.csimports 21 module namespaces and lists 33 tables.- Controllers and validators are already found by ASP.NET itself, and mappers are static helpers, so they need no list.
25 of 64 pull requests edited a shared file, but only 2 merges clashed on one
The git history from June 2025 to November 2026 holds 64 merged pull requests. This chart counts the pull requests that changed each shared file:
Show as table
| pull requests | |
|---|---|
| The snapshot | 21 |
| MainDbContext.cs | 19 |
| DomainServices.cs | 17 |
| Server.cs | 9 |
| Any of the four | 25 |
git history, measured
So about 4 in 10 pull requests touched at least one of them Measured.
All 94 merge commits were replayed with git merge-tree; 6 had conflicts. The service list and the table list caused one conflict each:
Show as table
| merges | |
|---|---|
| HttpClients.cs (a name list) | 3 |
| Settings files | 2 |
| DomainServices.cs | 1 |
| MainDbContext.cs | 1 |
| The snapshot | 0 |
94 merges replayed, measured
Pull requests that were rebased instead of merged leave no merge commit, so this undercounts Measured.
A migration is made on a laptop and applied by a separate program at deploy
A migration is written by EF when you run dotnet ef migrations add, and EF rewrites the snapshot at the same time. A migration bundle is a small program that only applies migrations.
The life of one migration, from the laptop to production:
- CreateA developer runs task migration:create. EF writes 2 new files (the migration and its Designer copy) and rewrites the snapshot.
- DeployCI builds a separate image that runs a migration bundle; a Kubernetes Job runs it before the app.
- LocalOn a developer cluster with AutoMigrate on, the app migrates itself at start.
- CINothing migrates a real database: the tests build their tables straight from the model. One test runs real migrations.
This is read from the code and the Taskfile From code. Today there are 15 migrations, which make 31 files, and the Designer files alone are 17,046 lines Measured.