{"push_id":2787948290,"size":1,"distinct_size":1,"ref":"refs/heads/patch-1","head":"eb58b48c4fab4dd927050c20cd13f1e9df7ee35e","before":"2f25f2bf04944e824bf738d1f4dbdec1c07b4de8","commits":[{"sha":"eb58b48c4fab4dd927050c20cd13f1e9df7ee35e","author":{"name":"Robin Maenhaut","email":"e7e50dbc0f35a389d53abc1d57ceb010d1bfe9d3@users.noreply.github.com"},"message":"Signal the implications of not moving migrations\n\nEF Core - Migrations - Seperate project\r\n\r\n1) When attempting to have migrations in a seperate project, the migrations assembly must contain at least one migration in order for the Add-Migrations command to find the DbContext.\r\nThis PR attempts to make the implication of not doing so more clear, as well as making it easier to find why things are breaking when you try to do this for an empty project.\r\n\r\n2) Fix a typo in MyStarupProject","distinct":true,"url":"https://api.github.com/repos/FUNExtreme/EntityFramework.Docs/commits/eb58b48c4fab4dd927050c20cd13f1e9df7ee35e"}]}
{"actor":{"display_login":"FUNExtreme"}}